-
Notifications
You must be signed in to change notification settings - Fork 29.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[v21.x] Revert "fs: remove workaround for esm
package"
#51390
[v21.x] Revert "fs: remove workaround for esm
package"
#51390
Conversation
per discussion at #51356 (comment), targeting v21.x-staging |
Before approving, do we have some docs about reverting changes? Should we actually revert or create a new commit with the change?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
According to reverting commits docs, you only need to include Fixes: #PR
in the PR message, can you update that?
esm
package"esm
package"
No need to modify the commit message for that, you can edit the PR description and it will be picked up by ncu and added to the commit message upon landing. But not sure if we use the same process for landing PRs on staging branches. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why revert it only to v21.x but not main?
Done |
@RafaelGSS Because the |
1c408b0
to
a8d2d56
Compare
Rebased to include jeremymeng@83f581d |
@jeremymeng rebased |
a8d2d56
to
3301a7d
Compare
77872eb
to
a5a17a1
Compare
This reverts commit 95b1989. It appears that the workaround is still needed: issue nodejs#51081
3301a7d
to
4368d29
Compare
Landed in f130a33 |
Fixes: #51081