NODE_ENV set to development on test.js config file

[pdfrod]

The file webpacker/lib/install/config/webpack/test.js is setting the environment to development. Shouldn't it be test?

[leonid-shevtsov]

I am concerned about this as well. Trying to get process.env.NODE_ENV to be test in my Capybara tests and the straightforward methods aren't working.

[PascalPixel]

Same issue here, had to set it to test to get capybara to pass (cors stuff)

// test.js

process.env.NODE_ENV = process.env.NODE_ENV || 'test'

const environment = require('./environment')
const config = environment.toWebpackConfig()

module.exports = config

[swrobel]

I was looking for the same, and it seems that node handles environments differently than Rails. There's discussion here, but the key quote is:

Webpack and node libraries only understands development and production environments.

[guillaumebriday]

Can this issue be closed ?

[Kukunin]

process.env.RAILS_ENV is available in my webpacker assets so I use it in my capybara tests.

Rails 6.1.3.2
webpacker 6.0.0.beta.7