-
-
Notifications
You must be signed in to change notification settings - Fork 26.9k
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
Bump resolve-url-loader version #9841
Conversation
Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. In order for us to review and merge your code, 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. If you have received this in error or have any questions, please contact us at [email protected]. Thanks! |
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks! |
Up! |
UP |
+1 🙏 |
only you can save us johannes |
UP |
+1 |
1 similar comment
+1 |
The discussion is happening on the linked issue. You’re welcome to participate in it if you have something substantial to add. But spamming the thread with “+1”s makes it less likely to be merged soon, not more. |
I've included this into |
Currently,
npm audit
fails because ofreact-scripts > resolve-url-loader > adjust-sourcemap-loader > object-path
.See #9840 for details.
This PR bumps the
resolve-url-loader
version from 3.1.1 to 3.1.2