-
-
Notifications
You must be signed in to change notification settings - Fork 15.2k
Migrate to yarn workspaces #4562
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
Conversation
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 0e6c4db:
|
We don't actually have any subpackages in here that would need workspaces. What are you trying to work on? |
Sorry, I should have explained this in the PR description. I turned the examples into workspaces. This allows them to be treated as workspaces, meaning they can use yarn and can be tested easily. |
Honestly, most of those examples are obsolete and need to be rewritten or deleted. We also don't want to generally install them when you clone the repo and set it up. What's the background on this effort? |
Oh, okay. I was not aware of that.
I was just looking for an open source project to contribute to 😅, nothing else. I'm still learning React & Redux, and I was checking out your repo and noticed the recent migration to Yarn, and noticed that the existence of |
Ah, gotcha. Yeah, there's an issue from 3 years ago I had filed saying "we really ought to rewrite the examples": and then not much happened with it. Honestly, the main things we could use help with atm are docs, across all 3 of our repos: as well as testing of the beta versions of our libs in various environments as we work towards the upcoming major releases. |
Okay, I'll try to contribute towards that too, but I think this PR could serve as a good starting point, because it simplifies the way examples are handled (Through the package manager instead of custom scripts), so future improvements can build on top of these cleanups. If you think this doesn't make sense, I can close this PR 😃 and focus more on other doc improvements in the future. |
PR Type
Does this PR add a new feature, or fix a bug?
Feature
Why should this PR be included?
It makes development experience better.
Checklist
New Features
This PR makes the examples use yarn instead of NPM.
What new capabilities does this PR add?
What docs changes are needed to explain this?