4 ms·
If you're willing to go whole hog into pnpm, rush.js is really nice. You get a single unified node_modules and lock file for your entire repo with individual no
by moojd 4y ago
If you're willing to go whole hog into pnpm, rush.js is really nice. You get a single unified node_modules and lock file for your entire repo with individual node_modules for each app/package projected with symlinks and local packages automatically symlinked together. We also have it set up so that when we push to our develop branch it builds, tests and bumps a prerelease version for only changed packages and dependents.
- yodon 4y agoRushJS looks amazing, thanks for mentioning it.
- seibelj 4y agoMy company has a large typescript monorepo with many (~100) devs all committing to it daily. We use rush and pnpm (and eslint and some other stuff). Very solid repository. No complaints. Pleasant to work in
- andrew_ 4y agoRush is great. But you're absolutely right. It is whole-hog and very prescriptive. I personally prefer being closer to the bare metal and using pnpm straight up.
- moojd 4y agoAbsolutely. I just want to echo this for anyone in this thread considering using rush. Straying from the way rush wants to do things will bring pain. It is definitely not a good fit for every project but embracing it has solved a ton of problems for us (having tons of duplicated node_modules directories bringing intellij to it's knees, keeping versions in sync, path resolution, publishing, deployment)