You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since #1395 got closed, continuing the discussion here because this problem needs to be fixed.
With the change introduced in d8dd446 , running rake assets:precompile breaks our CI since it always loads the config/webpack/production.js instead of the test.js file, causing the CI to error out since the code in that file does not have the required ENV variables available.
Explicitly setting NODE_ENV=test or RAILS_ENV=test has no bearing whatsoever on webpacker.
The only way we can currently get our assets compiled is by running RAILS_ENV=test NODE_ENV=test ./bin/webpack
The text was updated successfully, but these errors were encountered:
Since #1395 got closed, continuing the discussion here because this problem needs to be fixed.
With the change introduced in d8dd446 , running
rake assets:precompile
breaks our CI since it always loads theconfig/webpack/production.js
instead of thetest.js
file, causing the CI to error out since the code in that file does not have the required ENV variables available.Explicitly setting
NODE_ENV=test
orRAILS_ENV=test
has no bearing whatsoever on webpacker.The only way we can currently get our assets compiled is by running
RAILS_ENV=test NODE_ENV=test ./bin/webpack
The text was updated successfully, but these errors were encountered: