'assets:precompile' does not install devDependencies

[paulgeisler]

What's the reason behind installing node modules only from 'dependencies' through the '--production' flag?

webpacker/lib/tasks/webpacker/yarn_install.rake

Line 4 in 227661b

system "yarn install --no-progress --frozen-lockfile --production"

I do have some dependencies which are needed to build the app and are declared as 'devDependencies' (for example 'sass-resources-loader'). Another mate had to put all the testing clobber into 'dependencies' because the modules were missing in the test environment (after 'assets:precompile' ) which is semantically wrong.

It was really confusing and hard to find out because i've never experienced this routine for installing/building JS apps. There are always the 'yarn / npm install' commands in the instructions.

Usually there are a lot of transpilers in 'devDependencies' (babel, coffeescript, pug ...) so how does it work without them or should those be moved to 'dependencies' 🤔❓

It's not even analogue to Rails 5.1 yarn:install.
https://github.com/rails/rails/blob/v5.1.2/railties/lib/rails/tasks/yarn.rake#L4
system("./bin/yarn install --no-progress")

I would appreciate some clarification (and maybe a little lesson about dependencies declaration). 🙂

[gauravtiwari]

@paulgeisler Please see this issue: #160 and #117

Also see, https://yarnpkg.com/lang/en/docs/cli/install/#toc-yarn-install-production-true-false

We should probably remove the production flag but either way if NODE_ENV is set to production only the modules listed in dependencies section would be installed. So, please consider moving build modules to dependencies section.

[paulgeisler]

I see... Thanks! :)