-
Notifications
You must be signed in to change notification settings - Fork 582
Comment in and fix reportNonDefaultExport #676
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
Conversation
...odule/compiler/es6ImportDefaultBindingFollowedWithNamespaceBindingWithExport.errors.txt.diff
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I might be wrong but I think this regression is due to getEmitSyntaxForModuleSpecifierExpression
not being implemented, but they're just getting surfaced by these changes. Should I aim to implement that as well to confirm that theory in this PR? I'm torn between scope of changes and want for confidence
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If it's straightforward, what you have I think is already an improvement.
What is here seems correct, save for a couple of go-specific nits which I don't think really matter. |
Yeah, to go further we need |
Unlocked by implied node format