Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

install npm --production gives same result as without --production #74

Closed
fMads opened this issue Aug 3, 2016 · 3 comments
Closed

install npm --production gives same result as without --production #74

fMads opened this issue Aug 3, 2016 · 3 comments

Comments

@fMads
Copy link

fMads commented Aug 3, 2016

When running
npm-cache install npm --production
if you later run without --production on same package.json-file you get the same result

Ex
have a package.json file with devDependencies
run: npm-cache install npm --production
delete node_modules folder
run: npm-cache install npm
then node_modules doesn't container devDependencies

@rhys-eventbase
Copy link

I have noticed this also. I thought it was resolved in #63 but it still appears to install dev dependencies regardless of argument or not

@sod
Copy link
Contributor

sod commented Oct 12, 2016

I guess your cachefile already exists and was created without --production

one forceRefresh will redo the cache

rm -r node_modules
npm-cache install --forceRefresh npm --production

Maybe the command with arguments should be part of the cache hash.

@swarajban
Copy link
Owner

+1 to @sod . If someone wants to fix up the PR in #78, that might be the best option

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants