We check our node_modules folder into source control
jackfranklin.co.uk
We check our node_modules folder into source control
1–10 of 241 posts
Re: We check our node_modules folder into source control
#2Note to self: don't have dependencies. oh, wait, I don't ha
Re: We check our node_modules folder into source control
#3This very week I was dealing with my artifacts exploding in size because AWS got 429s from GitHub. Then Composer pulled from source and there were so many extra files and SCM folders we exceeded the max artifact size.
Another idea is to host your own package cache. That would be my preference where SCM size prohibits checking in dependencies themselves.
Re: We check our node_modules folder into source control
#4Perhaps you could achieve the best of both worlds by checking node_modules into a git submodule
Re: We check our node_modules folder into source control
#5[deleted]
Re: We check our node_modules folder into source control
#6> Once you check your node_modules in, there's no need to run an install step before you can get up and running on the codebase
Is this really true for packages with pre/post install scripts?
Re: We check our node_modules folder into source control
#7No, this is what the lock file is for.
Re: We check our node_modules folder into source control
#8> Once you check your node_modules in, there's no need to run an install step before you can get up and running on the codebase Is this really true for packages with pre/post install scripts?
No it's not. They are talking about their personal preference and it has nothing to do with real life employers.
Re: We check our node_modules folder into source control
#9No, this is what the lock file is for.
"I delete my lock file" is so common that I would say it has no value.
Re: We check our node_modules folder into source control
#10Does the Chrome DevTools team use Google's big monorepo and all the tooling around it? If so, that puts the author in a different situation than the vast majority of devs.