[Suggestion] Restructure ReactXP as a lerna monorepo to facilitate testing internal projects

[luisnaranjo733]

I think maintaining ReactXP would be easier if it were structured as a lerna monorepo.

Example scenario today:

• You make a breaking change to the XP source
• You want to add a test case to test your test project to test this change, but this project uses a published version of XP, so you can only test by manually building XP and copying the source over to node_modules.

Same scenario with a lerna monorepo

• You make a breaking change
• Changes will be automatically available in node_modules of the internal project because lerna bootstrap symlinks node_modules for you

For example, see this snippet from Wix's Detox framework contribution guide

For all the internal projects (detox, detox-cli, demos, test) lerna will create symbolic links in node_modules instead of npm copying the content of the projects. This way, any change you do on any code is there immediately. There is no need to update node modules or copy files between projects.

[erictraut]

I don't know if lerna is the answer, but I agree that this is a problem. Another potential solution is to have the RXPTest sample directly import from the core ReactXP sources rather than importing the published version.

[fbartho]

I'm motivated to get some sort of improved tooling for testing, but I think we can get that done with simpler tools than lerna.

Was there anything further you wanted to request in this ticket @luisnaranjo733 ?

See also #1233

[luisnaranjo733]

Nope! My intent was to outline the problem, not to be prescriptive about the solution. Thanks!