Uh oh!
There was an error while loading. Please reload this page.
[v21.x] Revert "fs: remove workaround for esm package" - #51390
Conversation
jeremymeng
commented
Jan 6, 2024
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?
H4ad
left a comment
There was a problem hiding this comment.
According to reverting commits docs, you only need to include Fixes: #PR in the PR message, can you update that?
nodejs-github-bot
commented
Jan 10, 2024
esm package"esm package"aduh95
commented
Jan 10, 2024
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. |
RafaelGSS
left a comment
There was a problem hiding this comment.
Why revert it only to v21.x but not main?
jeremymeng
commented
Jan 10, 2024
Done |
targos
commented
Feb 15, 2024
@RafaelGSS Because the |
nodejs-github-bot
commented
Feb 15, 2024
1c408b0 to
a8d2d56Comparetargos
commented
Feb 20, 2024
Rebased to include jeremymeng@83f581d |
nodejs-github-bot
commented
Feb 20, 2024
nodejs-github-bot
commented
Feb 21, 2024
nodejs-github-bot
commented
Feb 21, 2024
nodejs-github-bot
commented
Feb 21, 2024
@jeremymeng rebased |
a8d2d56 to
3301a7dCompare77872eb to
a5a17a1CompareThis reverts commit 95b1989. It appears that the workaround is still needed: issue nodejs#51081
3301a7d to
4368d29Comparenodejs-github-bot
commented
Feb 27, 2024
marco-ippolito
commented
Mar 1, 2024
Landed in f130a33 |
Fixes: #51081