Skip to content
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

Closed
bradfordlemley opened this issue Jun 5, 2018 · 4 comments
Closed

react-scripts 2.0 breaks some monorepos #4569

bradfordlemley opened this issue Jun 5, 2018 · 4 comments
Milestone

Comments

@bradfordlemley
Copy link
Contributor

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

@gaearon gaearon added this to the 2.0.0 milestone Jun 5, 2018
@gaearon
Copy link
Contributor

gaearon commented Jun 5, 2018

Is #4092 sufficient to fix this?

@bradfordlemley
Copy link
Contributor Author

Yes, #4092 would fix this. #4570 is an alternative fix, added #4092 (comment) as discussion on the alternative fixes.

@bebbi
Copy link
Contributor

bebbi commented Jun 27, 2018

@gaearon @bradfordlemley I read #4092 again and think the required private mark still conflicts with the #4249 case, see this comment

@Timer
Copy link
Contributor

Timer commented Sep 26, 2018

Reverted for 2.0 release.

@Timer Timer closed this as completed Sep 26, 2018
@lock lock bot locked and limited conversation to collaborators Jan 18, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants