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
The text was updated successfully, but these errors were encountered:
linvain
changed the title
Document "env" option to eslint-import-resolver-webpack
Document "env" option for eslint-import-resolver-webpack
Jan 14, 2019
@linvain / @ljharb , I know this is closed, but before I file a new issue, is there a way to acknowledge that environment variables exist, but not set their value? Maybe I'm misunderstanding how to use that config. My complex webpack setup allows the user to pass in additional options on the command line, but it throws all kinds of errors as were mentioned in the beginning of this issue.
I use env variable in my webpack config:
This leads to a hell of errors:
The issue can be resolved by adding env option to resolver settings:
But this is not documented.
P.S.: Thanks @VladimirPal (#1043)
The text was updated successfully, but these errors were encountered: