NODE_OPTIONS compilation warning after upgrading to 7.x #488
Unanswered
robotfelix
asked this question in
Q&A
Replies: 1 comment 1 reply
-
How are you passing the values from .env file to your app? Are you able to provide your webpack config? Can investigate further if we have a reproduction case |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
After upgrading shakapacker from
6.6.0
to7.2.3
, I'm now getting warnings about conflicting values ofNODE_OPTIONS
I've tested and found:
NODE_OPTIONS="--trace-warnings"
in.env
and calling./bin/shakapacker-dev-server
=> warningNODE_OPTIONS
in.env
and calling./bin/shakapacker-dev-server
=> no warningNODE_OPTIONS="--trace-warnings"
in.env
and callingNODE_OPTIONS="--trace-warnings" ./bin/shakapacker-dev-server
=> no warningSo I think the changes made in #350 are conflicting with the
NODE_OPTIONS
configuration I have in a dotenv /.env
file and setting the value ofNODE_OPTIONS
before the .env file is be read.Ideally I wouldn't have to stop using the .env for configuring this value as it varies between projects.
Has anyone else encountered a similar problem and has a suggestion of how to fix it?
Beta Was this translation helpful? Give feedback.
All reactions