fix: require regular version in stubs #20
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.
When we stub files for environments that do not handle export maps very well, we
require
a transpiled CJS implementation and re-export it in a stub file that should be immediately overriden by thebrowser
orexports
fields inpackage.json
.At the moment we use the value from the
browser
overrides to work out which file we shouldrequire
the stub. The change here is torequire
the transpiled regular CJS version in the stub instead of the browser override.Turns out when Jest has
testEnvironment: 'node'
set it resolvesrequire
s to the stubs, ignoringexports
which loads browser-specific code into node with predictably incendiary results.