Menu
If I invoke yarn add <my-package>, Yarn will install both dependencies and devDependencies of <my-package>. Is it normal behavior ?
I checked the documentation but I couldn't find a way to prevent it from installing the development dependencies (which I don't need). I believe devDependencies are the dependencies that were used to compile the sources into the build scripts. And building my app I just need the builds.
556
yarn install --production[=true|false]Yarn will not install any package listed in devDependencies if the NODE_ENV environment variable is set to production . Use this flag to instruct Yarn to ignore NODE_ENV and take its production-or-not status from this flag instead.
If you have just checked out a package from version control, you will need to install those dependencies. If you are adding dependencies for your project, then those dependencies are automatically installed during that process.
The package is automatically listed in the package. json file, under the dependencies list (as of npm 5. previously, you had to manually specify --save ). When you add the -D flag, or --save-dev , you are installing it as a development dependency, which adds it to the devDependencies list.
In a nutshell, yarn install is the command used to install all dependencies for a project, usually allocated in the package. json file. In most scenarios it is because you cloned a project and need its dependencies installed to run it. On the other hand, yarn build is not a built-in command in the Yarn package manager.
Use --production=true (or simply --production or --prod for short). It is indeed normal behaviour; Yarn assumes you are in a 'development' context unless your NODE_ENV environment variable is set to 'production'.
Have a look at Yarn's documentation.
165
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
