#monorepos

1 month ago

📣 Interested in #typescript #monorepos ? Want to meet other people from the @rushstack.io community and learn how they build code?

This month's ⭐️Rush Hour⭐ ️video call is on Friday, February 6th at 11am Pacific Time!

Sign up for free using this link:
rushstack.io/community/ev...

1 1 0 0

2 months ago

Monorepo vs. Multi-Repo vs. Git Submodule vs. Git Subtree: A Complete Guide for Developers

📣 Interested in #typescript #monorepos ? Want to meet other people from the @rushstack.io community and learn how they build code?

This month's ⭐️Rush Hour⭐ ️video call is on Friday, January 9th at 11am Pacific Time!

Sign up for free using this link:
rushstack.io/community/ev...

1 1 0 0

Frontend Dogma

@frontenddogma.com

4 months ago

Monorepo vs. Multi-Repo vs. Git Submodule vs. Git Subtree: A Complete Guide for Developers, by (not on Mastodon or Bluesky):

https://archive.ph/AHiTd

#guides #architecture #monorepos #git #versioncontrol

1 0 0 0

Jamie Mason

@foldleft.bsky.social

4 months ago

syncpack 14.0.0-alpha.27 adds support for @pnpm.io "catalog:" specifiers and can read catalogs from pnpm and bun, more to follow in future versions github.com/JamieMason/s... #pnpm #monorepo #monorepos

5 1 0 0

nyxz

@nyxz-1.bsky.social

4 months ago

TypeScript project references | moonrepo The ultimate in-depth guide for using TypeScript in a monorepo effectively!

The best guide on #Typescript in #monorepos that I have found so far moonrepo.dev/docs/guides/...

4 0 0 0

4 months ago

📣 Interested in large #typescript #monorepos ? Want to meet other people from the @rushstack.io community and learn how they build code?

This month's ⭐️Rush Hour⭐ ️video call is on THURSDAY, November 6th at 11am Pacific Time!

Sign up for free using this link:
rushstack.io/community/ev...

3 1 0 0

5 months ago

📣 Interested in large #typescript #monorepos ? Want to meet other people from the @rushstack.io community and learn how they build code?

Our next⭐️Rush Hour⭐️video call is this Friday, October 3rd at 11am Pacific Time!

Sign up for free using this link:
rushstack.io/community/ev...

1 1 0 0

Folge 280 - Monorepos bei Uber: 👍 oder 👎? | Software Architektur im Stream Google hat vor langer Zeit Monorepos eingeführt. Uber berichtet über Tooling. Sind Monorepos eher gut oder schlecht?

5 months ago

#Monorepos bei Uber: 👍 oder 👎?
Aufnahme (Video / Audio Podcast) verfügbar!
#SoftwareArchitektur im #Stream

3 1 0 0

5 months ago

#Monorepos bei Uber: 👍 oder 👎?
#SoftwareArchitektur im #Stream
HEUTE 13:00 CEST
Mehr Informationen und Möglichkeit für Fragen:
software-architektur...

2 0 0 0

5 months ago

#Monorepos bei Uber: 👍 oder 👎?
#SoftwareArchitektur im #Stream
MORGEN 13:00 CEST
Mehr Informationen und Möglichkeit für Fragen:
software-architektur...

2 0 0 0

The Multi-Repository TypeScript Problem Navigating Type Safety Across Service Boundaries

5 months ago

#Monorepos bei Uber: 👍 oder 👎?
#SoftwareArchitektur im #Stream
Freitag 2025-09-26 13:00 CEST
Mehr Informationen und Möglichkeit für Fragen:
software-architektur...

2 0 0 0

Frontend Dogma

@frontenddogma.com

7 months ago

The Multi-Repository TypeScript Problem, by (not on Mastodon or Bluesky):

www.carrick.tools/blog/the-multi-repositor...

#typescript #monorepos

1 0 0 0

7 months ago

1/8 Monorepos are huge for AI agents.

Most meaningful changes cross contexts: they naturally span multiple traditional repo boundaries.

When AI can see AND modify across these boundaries, the value multiplies exponentially.

@nx.dev #monorepos #ai

1 1 1 0

Bazel and Beer · Luma Join Aspect Build for a friendly gathering centered around Bazel and beer!

8 months ago

Nx Cloud Onboarding Improvements YouTube video by Nx - Smart Repos - Fast Builds

We made the Nx Cloud onboarding simpler.

Enable remote cache, self-healing CI in a few simple steps.

@nx.dev #monorepos

www.youtube.com/watch?v=LG3X...

4 2 0 0

Brick appreciator

@arrdem.com

8 months ago

lu.ma/uq2wxvih #osssummit crew if you aren't at the social (scheduling fail) come join the Aspect crew for scheming about making tests and deploys better with #monorepos!

2 0 0 0

The Ingredients of a Productive Monorepo

9 months ago

Polygraph is about getting the benefits of monorepo WITHOUT the monorepo. Platform teams can standardize, enable visibility, and drive AI-powered transformations across hundreds of repos.

Sign up to learn more.

@nx.dev #monorepos

4 1 0 0

Frontend Dogma

@frontenddogma.com

9 months ago

The Ingredients of a Productive Monorepo, by @swgillespie@mastodon.social:

https://blog.swgillespie.me/posts/monorepo-ingredients/

#monorepos #versioncontrol #building #testing #cicd

1 0 0 0

How to NOT do monorepos ## Who _actually_ needs a monorepo? Monorepos exist to solve the problems that arise when you you have deeply coupled and interconnected projects. For example, Vue.js has many libraries that depend on it, like Vue-Router, Pinia, Vue-I18N, Vue-DevTools, Vue Test-Utils, etc. So when tweaking the internals of how Vue works, it's important to know that this new version of Vue won't break any of these other libraries, _before_ doing a new Vue release. Another example is Jest, a unit-testing library. It solves dozens of unique problems around unit testing. And consequently those unique problems have been isolated into their own independent repos solely focused on solving their one problem in a version controlled way, like Snapshot testing for example. These other libraries all live in the same monorepo as Jest to make sure that as each is updated, they all work together happily! Yay! ## Why you don't want a monorepo Though they do solve the problems outlined above they come with some drawbacks. In the past monorepos were notorious for not being able to run on Windows machines. However, with npm Workspaces, this is no longer the case. But if you are using a different monorepo tool (Yarn, Lerna, Turbo, etc). You _will_ have this problem. They just don't play nice on Windows computers. But you don't use Windows, and worse you're a selfish piece of shit that doesn't care about others, so this lack of support doesn't bother you (seriously, just use npm Workspaces, they're good). The real issue with monorepos is they have a ton of added complexity. It makes sense, you are combining all of the project setup complexity of all other projects into one system. So that requires it to be more complex than any of them would be on their own. Having multiple nested `package.json` files in a project also can cause issues with 3rd party tooling and editors. It's not always obvious where a dependency should be installed either. Initial setup of the repo is also much more cumbersome for new devs, as it requires a massive `npm install` to create a huge shared `node_modules`. Abstracting `npm scripts` across all your repos is more of a pain. Setting up publishing of all packages at the same time is a benefit but also complex, and results in much uglier and harder to use GitHub Releases pages. etc. etc. etc. It's a technology, it has pros and cons, big whoop. Some projects really do justify the need for this extra effort and hassle, but if you can avoid it, you should try your best to. ## You probably don't need a mono repo. Here's a case where you might _think_ you need one.... but nehhhh you don't. Let's say you have a component library. You'll need to be able to build this library to a "dist" folder, and publish it to npm (including the `package.json`). You'll also need to create a documentation website. As you write a new component, it would be nice to document it as you go, so you can see the component live in the docs site locally and play with it as you build it to make sure it works. This means that you will be updating the docs site and the component library in the same branch at the same time. Pretty convenient. But the docs site needs it's own build process. So it can create a "site" folder of static assets that gets deployed. How can we solve this _without_ all of the headache of a monorepo? How can we do this in a simpler way? ## Solution In this scenario the solution is actually pretty easy. Use multiple Vite config files. * `vite.config.lib.js` * This config file has all the build options for the `/lib` folder to create the `/dist` folder. It also has all the Vitest unit testing options for the component library set up. * `vite.config.docs.js` * This config file has all the build options for the `/docs` folder to create the `/site` folder. It also has options related to running the server locally for development. * In your `package.json` you will have different npm Scripts: like: { "scripts": { "start": "vite --config vite.config.docs.js", "build:docs": "vite build --config vite.config.docs.js", "build:lib": "vite build --config vite.config.lib.js", "test": "vitest --config vite.config.lib.js" } } * Then you can run `npm start` to start the docs site, or `npm run build` to build both the docs site and the library. ## Benefits/Drawbacks This system is dramatically simpler to deal with. It's just a few config files. However, the downside is you have one `package.json` for everything, and you'll need to put everything in the `"devDependencies"` section, unless you want users of your library to receive them when they `npm install` your library.

10 months ago

Nx 21 is now available with major upgrades across the board. Three key themes. Thread 👇

@nx.dev #monorepos #ai #smartrepo

2 1 1 0

Jamie Mason

@foldleft.bsky.social

10 months ago

# Only fix issues in dependencies and devDependencies syncpack fix --dependency-types prod,dev # Only fix inconsistencies with exact versions (eg "1.2.3") syncpack fix --specifier-types exact # Only fix issues in "react" specifically syncpack fix --dependencies react # See more examples syncpack fix --help # See a short summary of options syncpack fix -h

# Fix every formatting issue in the monorepo syncpack format # List all formatting issues in the monorepo syncpack format --check # Check the formatting of one package syncpack format --check --source 'packages/pingu/package.json' # See more examples syncpack format --help # See a short summary of options syncpack format -h

# Find all issues in "dependencies" or "devDependencies" syncpack lint --dependency-types prod,dev # Only lint issues in "react" specifically syncpack lint --dependencies react # Look for issues in dependencies containing "react" in the name syncpack lint --dependencies '**react**' # Find issues in scoped packages only syncpack lint --dependencies '@types/**' # Find issues everywhere except "peerDependencies" syncpack lint --dependency-types '!peer' # Only look for issues where an exact version is used (eg "1.2.3") syncpack lint --specifier-types exact # Sort dependencies by how many times they are used syncpack lint --sort count # See more examples syncpack lint --help # See a short summary of options syncpack lint -h

# Accept any update in latest (x.x.x) syncpack update --target latest # Only update minor versions (1.x.x) syncpack update --target minor # Only update patch versions (1.2.x) syncpack update --target patch # Check for outdated dependencies in one package syncpack update --check --source 'packages/pingu/package.json' # Update dependencies and devDependencies in the whole monorepo syncpack update --dependency-types dev,prod # Only update dependencies with a semver range specifier (^, ~, etc.) syncpack update --specifier-types range # Update dependencies where name exactly matches 'react' syncpack update --dependencies 'react' # Update dependencies where name contains 'react' syncpack update --dependencies '**react**' # Update dependencies with the '@aws-sdk' scope syncpack update --dependencies '@aws-sdk/**' # See more examples syncpack update --help # See a short summary of options syncpack update -h

It's still very much in alpha but the Rust rewrite of syncpack has come a long way. syncpack is a tool to manage @npmjs.bsky.social dependency versions in large #JavaScript or #TypeScript #Monorepos

Give it a try:
npx syncpack@alpha lint --dependency-types prod

github.com/JamieMason/s...

4 1 0 1

harshitpdoshi

@harshitpdoshi.online

10 months ago

the pain was real.
the config was gnarly.
but the developer experience now?

smooooooth.

would I recommend #monorepos? Yes — but only if you’re very patient and love debugging as much as building.

1 0 0 0

harshitpdoshi

@harshitpdoshi.online

10 months ago

#monorepos are cool… until they’re not.
I’ve spent the better part of last week deep in the weeds with a monorepo that houses:

- a @nextjs.org app
- an @expo.dev app
- a tamagui components library
- a @hono.dev server
- and an SST app for infra & APIs

all stitched together with shared code.

1 0 1 0

Forem

@forem.com.web.brid.gy

10 months ago

0 0 0 0

10 months ago

Nx + AI Integration YouTube video by Nx - Smart Monorepos - Fast CI

🎥15-min video:
Nx and AI - Why They Work so Well Together

The video could have been shorter if I had not spent time discussing the genie teleporting John Carmack to work at a bank.

@nx.dev #monorepos #ai

www.youtube.com/watch?v=_dPX...

2 2 1 1

10 months ago

Everyone measures CI, but what matters is "time to meaningful feedback." @nx.dev sends info the your already-broken-but-still-in-progress PR to your editor and your coding assistant. So you can fix it and force push it while your PR is running.

#monorepos #ai

3 0 0 0

11 months ago

🔥 Nx MCP ❤️ VSCode Copilot 8-Min Demo 🔥

I've been showing this to developers working on large systems, and they love it.

Nx MCP really helps with the narrowing of the context and predictability issues.

@nx.dev #Monorepos

1 0 0 0