docs: corrections for Nx page #10019
Merged
Conversation
This file contains hidden or 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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
tknickman
approved these changes
Feb 20, 2025
chris-olszewski
approved these changes
Feb 20, 2025
|
Forgot to link James' PR!: #10003 |
This was referenced Feb 20, 2025
1 task
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.
Description
@JamesHenry pointed out some inaccuracies on the Nx page, so correcting them here!
I apologize for these. I'm not an Nx expert and, as made more clear in this PR, the sections in the "Why switch?" come from Nx users looking to migrate. I tried my best to bring together their words, but missed the mark. Namely, I learned that Nx's plugins are optional to use and I mis-characterized how Nx's starter templates work.