dev-middleware: Update chromium-edge-launcher to ^0.3.0#51340
dev-middleware: Update chromium-edge-launcher to ^0.3.0#51340qwertychouskie wants to merge 1 commit into
chromium-edge-launcher to ^0.3.0#51340Conversation
|
Hi @qwertychouskie! Thank you for your pull request and welcome to our community. Action RequiredIn order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you. ProcessIn order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA. Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks! |
|
|
What's stopping this from going in? |
|
Is there a timeline for when it is going to be solved? |
|
There is a new version of |
|
Upgrading to 0.3.0 seems like a good no-regret idea! Upgrading further, to 2.x would also be good, to get both rimraf and mkdirp out of the dependency tree. The package is ESM-only at that version, but given the current Node version constraints of react-native that should not pose a problem, as require(ESM) is available in those Node versions. |
|
This PR is now a duplicate of #54711, which is merged. A new PR can be opened to look into modernizing further. |
Summary:
Update
chromium-edge-launcherto^0.3.0, which has been updated to no longer use some deprecated packages/versions.Changelog:
Changelog: https://github.com/cezaraugusto/chromium-edge-launcher/releases