feat(es/modules): Use function instead of arrow function unconditionally #7273
+7,828
−2,676
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
|
IMO, it's OK to remove this optimization. |
|
Thank you! |
kdy1
commented
Apr 15, 2023
![kodiakhq[bot]](https://avatars.githubusercontent.com/in/29196?s=60&v=4){kind=small}
kdy1
changed the title
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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:
I think the minifier will optimize this as an arrow function.
This is causing a problem in next.js, so I'm checking if this will fix it.
But basically, this is not our problem. Client files of next.js are compiled to
es2016but one of unit test in next.js expects the final app to be es5.@magic-akari I'm sorry to ask this, but do we really need this optimization in module transform?
Related issue (if exists):