You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently check in our production dependencies to git (which allows us to git checkout a full working version of our app on our production machines), and we don't check in our dev dependencies.
Until npm@3 we've been able to specify our dev dependency directories in our .gitignore:
There's a duplication here with what's listed in package.json and ideally there'd be a single line we could ignore (eg node_modules_dev or something), but up until npm@3 it wasn't too bad.
The issue under npm@3 is we have literally hundreds of packages at the top level that need to be ignored – and worse, I worry that we may ignore some only to have them needed for a production dependency down the track.
Is there anything we can do about this? Any npm command that I might be missing that will help us out? Any way to separate production from dev dependencies?
We currently check in our production dependencies to git (which allows us to git checkout a full working version of our app on our production machines), and we don't check in our dev dependencies.
Until npm@3 we've been able to specify our dev dependency directories in our
.gitignore:There's a duplication here with what's listed in package.json and ideally there'd be a single line we could ignore (eg
node_modules_devor something), but up until npm@3 it wasn't too bad.The issue under npm@3 is we have literally hundreds of packages at the top level that need to be ignored – and worse, I worry that we may ignore some only to have them needed for a production dependency down the track.
Etc...
Is there anything we can do about this? Any npm command that I might be missing that will help us out? Any way to separate production from dev dependencies?