fix: handle frozen default exports#120
Merged
imranbarbhuiya merged 1 commit intoimranbarbhuiya:mainfrom Jun 26, 2023
Merged
Conversation
imranbarbhuiya
approved these changes
Jun 26, 2023
1 task
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
We had a bug report against Remix: remix-run/remix#6665
When polyfilling
tty, I get the following error:After some digging, I discovered that this is because the JSPM polyfill for
ttylooks like this:The default export is a read-only object since it's been passed to
Object.freeze, and then the code injected by this plugin attempts to mutate it:I initially tried to fix the injected CommonJS code by using
Object.assign({}, polyfill.default, polyfill), but unless I'm missing something, I found that esbuild is able to handleexport *even when imported from a CommonJS file. Using ES modules to handle the re-export seems a lot cleaner since it avoids these sorts of issues entirely, otherwise we'd need to handle all sorts of edge cases when re-exporting.Status and versioning classification: