Ensure nested member expressions are marked used in dev mode #9258
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.
↪️ Pull Request
Currently with scope hoisting disabled, nested member expressions are not tracked for import usage correctly. This can cause runtime errors as the import is ignored when the module is side-effect free.
The fix is to ensure we continue to visit the nested member expressions until we find the root.
💻 Examples
Example where foo would not be marked as used:
🚨 Test instructions
✔️ PR Todo