feat: add support for import assertions #74
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.
Adds support for parsing import assertions.
Three variables are used -
"a"
,"as"
and"ae"
.For static imports these correspond to:
"a"
: The start of the"assert"
keyword in the static import statement"as"
: The{
start of the assertion"ae"
: The}
end of the assertionFor dynamic imports,
"as"
and"ae"
are not used, instead only"a"
:"a"
: The index immediately after the,
- so{
in the dynamic import expressionimport('specifier', {...})
"e"
: Is updated to reference the end of the specifier portion before the,
in the import expression, instead of the position before the closing)
. This is effectively a breaking change to the dynamic import handling."ss"
: Remains but is now documented as the start of the dynamicimport(...
expression itself."se"
: Is updated to reference the end of the import expression (position of the closing)
).Resolves #73.