-
Notifications
You must be signed in to change notification settings - Fork 98
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
test(test-repos): Add a test monorepo under /test-repos/yarn-pnpm #3507
base: main
Are you sure you want to change the base?
Conversation
"@rnx-repo-yarn-pnpm/eslint-config": "workspace:*", | ||
"@rnx-repo-yarn-pnpm/scripts": "workspace:*", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we use portal:
instead of copying these two packages?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The scripts will be not quite the same but I can make that adjustment for the eslint-config package.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The package folder should be all lower-case.
Description
There are several tools built in rnx-kit that it would be beneficial to test in a separate repo. This creates a separate monorepo, set up with yarn in pnpm mode under /test-repos/yarn-pnpm. This will allow us to leverage tools built in rnx-kit and test them out in various configurations.
Currently this test repo isn't included in CI loops, as it is pulling in rnx-kit packages via npm, but that will be added once it is in a nice state and is actually testing out some of the tools directly. Ideally it will reference the rnx-kit packages via the external workspaces plugin.
For the repo itself: