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
It turned out in #274 , that, when the target: "node" property is missing in the webpack configuration, the compiles mostly work, but are missing the environment variables.
For the user this is not obvious, but can be checked by the plugin easily. It would be a great UX improvement, if the plugin could warn about the missing setting and set it to "node" automatically if absent.
This is a Feature Proposal
Description
It turned out in #274 , that, when the
target: "node"
property is missing in the webpack configuration, the compiles mostly work, but are missing the environment variables.For the user this is not obvious, but can be checked by the plugin easily. It would be a great UX improvement, if the plugin could warn about the missing setting and set it to "node" automatically if absent.
Similar or dependent issue(s):
Additional Data
The text was updated successfully, but these errors were encountered: