This repository has been archived by the owner on Dec 8, 2024. It is now read-only.
Avoid sharing list of previously added imports. #355
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.
The test added here shows the underlying problem, when transpiling multiple files with a shared babel configuration (which is very normal), you would end up with failures if any transformation fails (all future transformations would continue to fail):
The fundamental issue here is that we shared the list of previously imported modules so that we can make sure their import bindings have been rewritten to use the babel-plugin-ember-modules-api-polyfill transformation. Unfortunately, we tracked that state in the closure state of the babel plugin. That babel plugin closure state is only evaluated / created once not once per-file.
This changes things to track the module imports that have been created on the local state (which is reset properly per "transpilation attempt").