Skip to content

fix(create-vite): update moved eslint-react plugin links in generated README - #23284

Merged
bluwy merged 2 commits into
vitejs:mainfrom
FirmaSpring:fix-create-vite-eslint-react-links
Aug 18, 2026
Merged

fix(create-vite): update moved eslint-react plugin links in generated README#23284
bluwy merged 2 commits into
vitejs:mainfrom
FirmaSpring:fix-create-vite-eslint-react-links

Conversation

@FirmaSpring

Copy link
Copy Markdown
Contributor

Problem

In packages/create-vite/src/index.ts, the generated README for React templates links to the eslint-react plugin directories at the old packages/plugins/ location:

  • https://github.com/Rel1cx/eslint-react/tree/main/packages/plugins/eslint-plugin-react-x
  • https://github.com/Rel1cx/eslint-react/tree/main/packages/plugins/eslint-plugin-react-dom

Both URLs now return 404. The eslint-react repository restructured and the plugins now live under plugins/, which can be confirmed in the repository tree:

  • https://github.com/Rel1cx/eslint-react/tree/main/plugins/eslint-plugin-react-x
  • https://github.com/Rel1cx/eslint-react/tree/main/plugins/eslint-plugin-react-dom

This affects every newly scaffolded React project that reads its generated README.

Solution

Update both links to the current plugins/ paths in the template text used to generate the README.

Verification

  • curl -L -o /dev/null -w "%{http_code}" on the old URLs returns 404
  • The same check on the new URLs returns 200
  • git diff --check passes; only the single template line changes

… README

The eslint-react repository restructured its plugins into the plugins/ directory, so the old packages/plugins/ paths now return 404.

Co-authored-by: FirmamentalSpring <287222957+FirmaSpring@users.noreply.github.com>
btea
btea previously approved these changes Aug 17, 2026
@bluwy

bluwy commented Aug 18, 2026

Copy link
Copy Markdown
Member

Can we update these to npmx links? Like https://npmx.dev/package/eslint-plugin-react-x. Since we mention installing these packages, I think it makes more sense to link to registry pages.

Link the generated README install hints to the npm registry pages,
as requested in review.

Co-authored-by: FirmamentalSpring <287222957+FirmaSpring@users.noreply.github.com>
@FirmaSpring

Copy link
Copy Markdown
Contributor Author

Updated the generated README links to the npmx registry pages:

Both return 200.

@bluwy bluwy left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@bluwy
bluwy merged commit 1cbf7d6 into vitejs:main Aug 18, 2026
17 of 18 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants