Account for modules without importNames #1097
Merged
Conversation
This file contains 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
importNames is used for tree-shaking, but non-ES modules will not have this metadata. Previously we assumed anything with `importSpecifiers` also had `importNames`, but this isn't the case; stache files have the specifiers metadata which is used for error reporting.
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.
importNames is used for tree-shaking, but non-ES modules will not have
this metadata. Previously we assumed anything with
importSpecifiersalso had
importNames, but this isn't the case; stache files have thespecifiers metadata which is used for error reporting.
This fixes a regression in steal-tools 2.0.8.