React-vite: Fix perf regression by pinning vite-plugin-react-docgen-ts

[shilman]

Closes #22011

What I did

It seems as if joshwooding/vite-plugin-react-docgen-typescript#17 might have caused a huge performance regression. This is likely causing problems for end users and might also be what has broken CI for the storybook repo.

How to test

• CI passes

[socket-security]

New dependency changes detected. Learn more about Socket for GitHub ↗︎

---

👍 No new dependency issues detected in pull request

Bot Commands

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of package-name@version specifiers. e.g. @SocketSecurity ignore foo@1.0.0 bar@* or ignore all packages with @SocketSecurity ignore-all

Pull request alert summary

Issue	Status
Install scripts	✅ 0 issues
Native code	✅ 0 issues
Bin script confusion	✅ 0 issues
Bin script shell injection	✅ 0 issues
Shell access	✅ 0 issues
Uses eval	✅ 0 issues
Unresolved require	✅ 0 issues
Invalid package.json	✅ 0 issues
HTTP dependency	✅ 0 issues
Git dependency	✅ 0 issues
GitHub dependency	✅ 0 issues
New author	✅ 0 issues
Potential typo squat	✅ 0 issues
Known Malware	✅ 0 issues
Telemetry	✅ 0 issues
Protestware/Troll package	✅ 0 issues

---

📊 Modified Dependency Overview:

⬆️ Updated Package	Version Diff	Added Capability Access	+/- Transitive Count	Publisher
@joshwooding/vite-plugin-react-docgen-typescript@0.2.1	0.2.2...0.2.1	None	+1/-0	joshwooding

[dhess]

I can confirm that by using a pnpm override in our package.json, pinning this package to 0.2.1 fixes #22011.

[IanVS]

joshwooding/vite-plugin-react-docgen-typescript#17 is the change upstream that seems to have caused the issue.

@valentinpalkovic @joshwooding we may need to take another swing at this.

[htmlin]

https://github.com/joshwooding/vite-plugin-react-docgen-typescript/releases/tag/v0.2.3
It seems that joshwooding/vite-plugin-react-docgen-typescript has released a new version to fix the problem. Can we upgrade it again?

[IanVS]

We can but so far it's identical so there's no need. A new version is coming soon to support vite 5, then we'll update.