| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
PR-URL: nodejs#50987 Reviewed-By: Geoffrey Booth <webadmin@geoffreybooth.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Jacob Smith <jacob@frende.me> Backport-PR-URL: nodejs#51989
|
cc @nodejs/releasers |
Sorry, something went wrong.
|
Is it a clean cherry-pick? If that's the case, a backport PR shouldn't be necessary. We use lts-watch- label to bring PRs to the attention of releasers. |
Sorry, something went wrong.
It is clean cherry-pick, is there a way for me to add label? I assume there's some permission that prevents label spam from people that are not maintainers. |
Sorry, something went wrong.
|
I've added the labels. |
Sorry, something went wrong.
Thank you! |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Refs: #50987
Fixes: #50878
I confirmed that Wrapping a require of an ES module while using --abort-on-uncaught-exception fails without the fix
PS. I read through Backporting release lines and Contributing and I'm still not sure what should I do to get the fix backported.
a) Is it still "baking", is the process automated so should I just wait a bit more?
b) Should I just add some label backport-requested-vN.x and because there are no conflicts it will be automatically backported? I guess it's not possible.
c) Was it decided that fix shouldn't land in LTS?
Please let me know if I should close this PR and request it some other way. :)