Add monorepo setup recipe tailored for Ignite #173
+809
−0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fpena
changed the title
This was
linked to
issues
Sep 13, 2024
joshuayoes
reviewed
Sep 30, 2024
joshuayoes
approved these changes
Sep 30, 2024
There was a problem hiding this comment.
These are phenomenal guides @fpena. This has been a big topic to cover but you've have done a great job capturing all of our feedback and more.
I look forward to linking to these articles in community discussions.
Co-authored-by: Joshua Yoes <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Description
This PR introduces a guide for creating a Yarn mono repo tailored for React Native projects using the Ignite framework. The focus is on establishing a mono repo structure that accommodates shared utilities across multiple applications, such as a common ESLint configuration and a shared UI components library.
In detail, the guide includes:
apps/andpackages/folders, optimized for shared code and dependencies across multiple projects.Lastly, there's a document with guidance on choosing the right mono repo strategy, including when to adopt or avoid a mono repo, standard tools (Yarn Workspaces, Nx, Turborepo), and typical setups that align with specific project needs.