-
-
Notifications
You must be signed in to change notification settings - Fork 413
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: import parsing #259
feat: import parsing #259
Conversation
5372370
to
bc205c5
Compare
Thanks for picking this up |
You need to rebase |
This isn't really spec compliant, but it works fine for the time being. Things like multiple default imports are parsed without error. This example isn't supposed to be valid, but it parses fine: import default, defaultTwo from "./somefile.js"; I'm not to concerned with this currently. I would prefer to move on to export parsing and revisit this once module execution works. |
Hi! The parser has changed a lot after #281. Would it be possible to rebase? |
pings @afinch7 we may have to close this PR if it becomes inactive |
Not perfectly spec compliant yet, but should be close enough until import execution is implemented.
I should have some time this week to get this completely rebased. |
I haven't been able to find the time to rebase this right now. I'm closing for now. |
Simple import statement parsing. I intend to follow this up with some execution implementation.