Improved default export analysis #85
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
🦋 Changeset detectedLatest commit: 959229e The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Merged
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.
Fixes #10
Previously,
FalseExportDefaulthad many cases of false positives where the JavaScript assigned an object tomodule.exports, and that object had adefaultproperty pointing back to itself. This pattern is not a trueFalseExportDefault, but it is still problematic if the types only declare anexport default. These kinds of false positives ofFalseExportDefaultare now instead reported asMissingExportEquals.Additionally,
FalseExportDefaultwas only ever reported as being visible innode16-esm, but this was incorrect. The consequences are most likely to be visible innode16-esm, but the problem is fundamentally independent of the module resolution mode, and inaccuracies can be observed in other modes as well, especially whenesModuleInteropis not enabled.