Install dependencies in production mode before deploying
See original GitHub issueRight now we are just deploying the app as it is, but npm
supports installing the deps in production mode, which halves the size of the zip at least by half.
Issue Analytics
- State:
- Created 3 years ago
- Comments:11 (11 by maintainers)
Top Results From Across the Web
How to Install Node.js Dependencies for Production ...
NPM offers an option which allows to only install app dependencies required for production environment. Use one of the following commands to ......
Read more >Installing Dev Dependencies with npm: Beginners' Guide
Dependency is an object that contains the library, which your project requires for production environments and functioning effectively.
Read more >How do you prevent install of "devDependencies" NPM ...
The npm install command will install the devDependencies along other dependencies when run inside a package directory, in a development environment (the ......
Read more >Do npm dependencies and devDependencies effect your ...
A: Both dependencies and devDependencies are installed to the local node_modules folder on a yarn install or npm install , but only dependencies...
Read more >Installing dependencies | Yarn
yarn install is used to install all dependencies for a project. The dependencies are retrieved from your project's package.json file, and stored in...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@sanskar-p then I’d change the type of
config
toBoosterConfig
.The project dir would
process.cwd()
because its where the user will use the tool. We cannot assume that the name will bebooster
because we don’t know the project name of the user in that point, but we can assume that it will be executed from the root of the projectYes, what @Fecony said it is right. The scripts folder doesn’t exist when the user installs the CLI tool, it has to be inside of the command like @Fecony pointed