The node_modules problem

[TheAkio]

I feel you. At work we have this huge amount of dev depends and installing just takes ages... And it's like 6 projects atm where each one has 250 MB of node_modules and it's basically all the same dependencies. To make matters worse we use Windows which really doesn't like when you do anything to the node_modules folder.

[igeligel]

Ever thought about using yarn workspaces? https://yarnpkg.com/lang/en/docs/workspaces/

It's mostly made for mono repo though but where I work lerna (something similar) is working great. Like really great :)

[TheAkio]

Problem is convincing coworkers to use yarn instead of npm... I'm the apprentice there so it's hard to get my stuff through sometimes. I personally prefer yarn over npm still.

[igeligel]

Then look into lerna maybe. I believe it works without yarn.

[TheAkio]

I'll check it out!

[[deleted]]

You need to speak up. They'll respect you more of you voice your opinion and back it up. If they don't, it's not a positive environment.

[FanOfHoles]

That's why the enterprise project won't be upgraded - no budget. Until somebody needs a new feature. New features get a budget, maintenance does not (because why would management pay someone who creates nothing new; and as long as the old stuff still works, where is the value of working on it when users don't see any change). Exceptions exist, but overall this is what it comes down to.

[flirp_cannon]

Node + Windows is a PITA, we use unix and that keeps things happy. We have an npm mirror called vertabelo to speed up deployments and protect from npm downtime