-
-
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
Allowing "file:<path>" --scripts-version values #3629
Conversation
c11189b
to
850c5cc
Compare
850c5cc
to
707e5b8
Compare
OK. I can't promise we won't break this in the future, but doesn't hurt to get it in. |
Understandable, thanks! |
This is out! Please let us know if something doesn’t quite work. |
Trying to get this to work. I've gone into my custom 'react-scripts' directory (after forking this repo and cloning it - nothing edited) and ran
Any ideas what I'm missing? |
@leepowellcouk instead of |
I'd note our local development workflow might be broken right now due to recent changes. If you file a separate issue for that, it would be nice. We had a |
Looked like it was a corrupt react-scripts for me, for some reason a couple of deps had failed. Cleaned it all down, started again and it works great. Thanks for all the hard work that goes into this tooling! |
* Allowing for local "file:" prefixed scripts packages * Fixing test failure
This change is useful for testing local changes to scripts packages before committing them.
e. g.
I verified these changes by running
npm link
inside the create-react-app package and then runningcreate-react-app my-app --scripts-version=file:./create-react-app/packages/react-scripts
.