Force install of devDependencies #182
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The idea of the buildpack is to install `devDependencies` even if the `NODE_ENV` is set to `production` simply avoiding the flag `--production` on `npm install`. Unfortunately this doesn't work since npm never installs `devDependencies` if the environment is set to `production`. To fix that we can run npm install as `development`
|
Any news on this one? @yourcelf |
chdsbd
approved these changes
Aug 27, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The idea of the buildpack is to install
devDependencieseven if theNODE_ENVis set toproductionsimply avoiding the flag--productiononnpm install.Unfortunately this doesn't work since npm never installs
devDependenciesif the environment is set toproduction. Official documentation states:To fix that we can run npm install as
development.