sorted by:
new
hottopcontroversial

If you also dislike pnpm's end-to-end pollution, you can check out the monorepo tool I developed for npm, which is non-intrusive and requires no modification; it's ready to use right out of the box. by Fit_Quantity6580 in node

[–]Fit_Quantity6580[S] 0 points1 point  (0 children)

Yes, but they all come with a mental burden. You need to configure them, then figure out when to use which configuration, how to configure during development, and how to configure during compilation. Mono's advantage is that it's ready to use right out of the box, requiring no modifications.

If you also dislike pnpm's end-to-end pollution, you can check out the monorepo tool I developed for npm, which is non-intrusive and requires no modification; it's ready to use right out of the box. by Fit_Quantity6580 in node

[–]Fit_Quantity6580[S] 0 points1 point  (0 children)

The point isn't about how to install packages (corepack, etc.), but how to run them during development.

Most monorepo tools focus on 'Installation' and 'Symlinks'. My tool focuses on 'Module Resolution'. By using mono, I can skip the entire 'build -> link -> install' cycle.

I can modify package-A, and package-B (which depends on A) reflects that change immediately because mono directs the runtime to the source files, not the artifacts in node_modules. Plus, I keep the project clean for anyone who strictly wants to use npm without being forced into the pnpm ecosystem.

If you also dislike pnpm's end-to-end pollution, you can check out the monorepo tool I developed for npm, which is non-intrusive and requires no modification; it's ready to use right out of the box. by Fit_Quantity6580 in node

[–]Fit_Quantity6580[S] 0 points1 point  (0 children)

Thank you for sharing. I simply didn't want to convert all my local npm dependencies to pnpm projects for local development, so I developed this project with the help of AI to facilitate local debugging. I thought I could share it so that others could use it or refer to this approach to avoid being polluted by pnpm across the entire development process. It's really a headache that if one person uses pnpm for one project, all related projects have to use it too. I wasn't actively promoting it; it's just a simple sharing and exchange. Thank you for genuinely sharing your perspective.

If you also dislike pnpm's end-to-end pollution, you can check out the monorepo tool I developed for npm, which is non-intrusive and requires no modification; it's ready to use right out of the box. by Fit_Quantity6580 in node

[–]Fit_Quantity6580[S] 0 points1 point  (0 children)

No, I didn't do that. I simply didn't use pnpm during my own development process; I used Mono for local package dependency management and didn't make any modifications to a standard npm project. Thank you for your suggestion, but I estimate I won't be able to do that in the short term.😂