Question: can the build error if variables are not found?
Open
- Dominant language
- JavaScript
- Stars
- 895
- Forks
- 57
- PR merge metrics
- No merged PRs in 30d
Description
I'm not sure if there is already an option for this, but if not, it would be nice if we could choose to have the build error when trying to replace `process.env.WHATEVER` if the variable is not defined (falsey?).
Similar to https://webpack.js.org/plugins/environment-plugin/
> If an environment variable is not found during bundling and no default value was provided, webpack will throw an error instead of a warning.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.