You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since monorepo support was reverted on v2 release, some of my projects are stuck in pre-release, which is not durable. I need a robust solution to share modules with all the CRA projects of the monorepo, in a dev-friendly way. Looking at CRA issues, it seems that i'm not alone in this situation.
Describe the solution you'd like
@Timer said in the Completion roadmap for react-scripts@2.0 (5024 - 3) :
"We're going to revert monorepo support in favor of consuming library packages via nwb and provide excellent documentation on how to do so. This is arguably the best way."
This documentation would be so useful... Is this still planned?
(And really, thanks for this incredible and really useful work !)
The text was updated successfully, but these errors were encountered:
Is your proposal related to a problem?
Since monorepo support was reverted on v2 release, some of my projects are stuck in pre-release, which is not durable. I need a robust solution to share modules with all the CRA projects of the monorepo, in a dev-friendly way. Looking at CRA issues, it seems that i'm not alone in this situation.
Describe the solution you'd like
@Timer said in the Completion roadmap for react-scripts@2.0 (5024 - 3) :
"We're going to revert monorepo support in favor of consuming library packages via nwb and provide excellent documentation on how to do so. This is arguably the best way."
This documentation would be so useful... Is this still planned?
(And really, thanks for this incredible and really useful work !)
The text was updated successfully, but these errors were encountered: