-
-
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
react-scripts 2.0 breaks some monorepos #4569
Milestone
Comments
Is #4092 sufficient to fix this? |
This was referenced Jun 5, 2018
Yes, #4092 would fix this. #4570 is an alternative fix, added #4092 (comment) as discussion on the alternative fixes. |
@gaearon @bradfordlemley I read #4092 again and think the required |
Reverted for 2.0 release. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Is this a bug report?
Yes
Description
Certain monorepos (e.g. ones with nwb components) are incompatible with react-scripts 2.0, which means that certain existing monorepos (that currently work with react-scripts 1.0) will be broken with react-scripts 2.0.
This is because the current react-scripts 2.0 treats all packages in the monorepo that are included by the app as source packages (transpiled, linted, and tested), and there is no mechanism for opting them in or out.
The following issues are a result of not being able to opt packages in/out:
Steps to Reproduce
See issues above.
Reproducible Demo
See issues above, or:
https://github.com/bradfordlemley/cra-monorepo-examples/tree/optin
The text was updated successfully, but these errors were encountered: