rushstack VS rfcs

If you're looking to recreate the ease of a monorepo with eslint/prettier, I've used the rushstack eslint patch to ship an eslint package which is almost fully self-contained, not just config, but dependencies as well: https://github.com/microsoft/rushstack/tree/main/eslint/eslint-patch

I highly recommend rushstack. It’s a suite of tools for managing TypeScript monorepos. I use it at work and never want to go back to working without it.

https://rushjs.io/ and https://rushstack.io/

Rush Stack. It’s an opinionated, batteries-included toolset for working with large monorepos. It’s highly extensible and pluggable, and has built-in support for a lot of common tasks. My team uses it at work to support a couple dozen projects and at this point I can’t imagine managing a monorepo without it. It has significant adoption within and support from Microsoft, and monthly public dev meetings with contributors from a number of other companies, so I really don’t think it’s going to disappear any time soon. From what I’ve seen, it’s a very healthy project that’s continuing to grow in support and adoption.

Tools like Lerna, Bazel, Nx, Rush, Turborepo, to name a few. Lerna is probably the grand daddy of all monorepo tools. CRA, Babel, Jest are a few projects that use it. Bazel has been refined and tested for years at Google to build heavy-duty, mission-critical infrastructure, services, and applications. Turborepo is the monorepo for Vercel, the leading platform for frontend frameworks. These tools can help keep your monorepo workspaces fast, understandable and manageable.

We don’t use backend node, I work in a big typescript monorepo and use Typescript to build plugins for compiling, packing, and testing, leveraging Rush and Heft on the client side (https://github.com/microsoft/rushstack) run via node

I guess I'm not alone wishing that rush uses commit messages for change log generation. It's actually not so difficult (once it's done 😎).

See: ONNX/ONNX Runtime, VSCode, Rush, & countless others

To late to edit or delete my comment above but just to set it straight I just learned that the whole lerna debacle linked above was a nothing-burger aka “fake news”.

https://github.com/microsoft/rushstack/issues/673#issuecomme...

npm workspaces plus Wireit works far better than Lerna, in my experience.

https://github.com/google/wireit

Wireit's ability to specify actual script dependencies, do caching (and on Github actions), and it's long-running service script support make it much more useful and comprehensive than Lerna.

I agree that this should be built into npm. There's an RRFC for it here: https://github.com/npm/rfcs/issues/706

It's coming https://github.com/npm/rfcs/blob/main/accepted/0042-isolated-mode.md

This just got accepted as a proposal in NPM: https://github.com/npm/rfcs/pull/626

npm also plans to support pnpm-style node_modules

(I usually end up removing npm ci from CI/CD since I think it is way too slow and want to cache node_modules from previous builds; I'm waiting for https://github.com/npm/rfcs/issues/415 to land to make this fail-safe npm install --from-lockfile. Yarn does support this already)

I started following this problem from the discussion at npm about making install scripts opt-in. But install scripts are not the only threat, there are more ways for malicious actors: