You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It appears that #36 is stalled for now and is a tricky problem to solve.
Would it be possible just to return the start position of export statements?
My aim is to parse export statements in a file without parsing the entire file. With just the start position, this would be achievable without a lot of overhead:
Get start position of export statement from es-module-lexer.
Get slice of file content from start position of the export statement to end of the file.
Pass that slice to a parser with instruction to bail out after 1 statement.
From #36, it sounds like finding the start of export statements is the easy part, and would be inexpensive, but it's finding the end which is hard.
Would you consider supporting this as a stopgap until full export parsing is supported?
The text was updated successfully, but these errors were encountered:
It appears that #36 is stalled for now and is a tricky problem to solve.
Would it be possible just to return the start position of export statements?
My aim is to parse export statements in a file without parsing the entire file. With just the start position, this would be achievable without a lot of overhead:
es-module-lexer
.From #36, it sounds like finding the start of export statements is the easy part, and would be inexpensive, but it's finding the end which is hard.
Would you consider supporting this as a stopgap until full export parsing is supported?
The text was updated successfully, but these errors were encountered: