-
Notifications
You must be signed in to change notification settings - Fork 127
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NODE_ENV is undefined, triggers console error in production #273
Comments
@dafnarosenblum is there an update on this issue. I have the same problem when using @mapbox/mapbox-gl-directions 4.1.0 in create-react-app. Even setting NODE_ENV=production on my production machine doesn't resolve this issue. |
This is also true for Angular applications and I too have been unable to find a way to solve this. Anyone have any suggestions? |
Reporting this since we installed mapbox-gl-directions (4.1.0) in our React app too. Tried a bunch of things with how our webpack builds run and no fix found so far. |
We have the same console error in our production code. We used mapbox-gl-directions (4.1.0). It does not matter what application it is (Angular, React, Vue of whatever). |
I have same console error. I'm using mapbox-gl-directions v4.1.0. I think, I can't draw line, point and polygon with using draw tools because of console error |
Same problem. I'm using mapbox-gl-directions@4.1.1 |
create-react-app with webpack >=4, I'm getting:
You are currently using minified code outside of NODE_ENV === 'production'. This means that you are running a slower development build of Redux. You can use loose-envify (https://github.com/zertosh/loose-envify) for browserify or DefinePlugin for webpack (http://stackoverflow.com/questions/30030031) to ensure you have the correct code for your production build.
From mapbox-gl-directions.js:5436 in production.
Adding process.env.NODE_ENV to the string in line 5413 results with printing undefined.
Adding process.env.NODE_ENV to the console.error in line 5436 results with printing 'production'.
I was wondering if there is a way to avoid this error in the log. Thanks.
The text was updated successfully, but these errors were encountered: