fix: de-confuse Nuxt build tooling by not using 'export *' in comments #5227
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.
Which problem is this PR solving?
See #5218. Using
export *
in comments breaks some build tooling (specifically the tooling used by Nuxt) and breaks the build output.Note for reviewers: This is weird and this is difficult to test, please use the reproducer I created for verifying that this actually fixes the problem. I also did not believe it at first when I narrowed it down to a comment. 😅
Fixes #5218
Short description of the changes
changes
export *
in comments to readwildcard export
insteadType of change
How Has This Been Tested?