allow to see exports for non-enumerable properties #4783
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
10 Ignored Deployments
|
kwonoj
approved these changes
May 2, 2023
|
✅ This change can build |
|
sokra
force-pushed
the
sokra/non-enumerable-exports
branch
from
19763cf
to
06f6fd6
Compare
kodiakhq bot
pushed a commit
to vercel/next.js
that referenced
this pull request
May 3, 2023
### What? test case for vercel/turbo#4783
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.
Description
enumerate all properties for namespace object creation.
This follows the webpack logic
test cases in vercel/next.js#49106
fixes WEB-976