fix: Guard against process
not being defined
#68
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What: Check for
process
being defined.Why: Webpack 5 doesn't shim Node's
process
object by default anymore. Only instances ofprocess.env.NODE_ENV
are replaced statically. This means that unguarded checks ofprocess.env
will crash in browser environments (such as Karma).How: Check for
process
being defined. This is a port of testing-library/react-testing-library#911Checklist: