-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
chore(react): Inline hoist-non-react-statics package
#18102
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
base: develop
Are you sure you want to change the base?
Conversation
b28862f to
4cfaf34
Compare
node-overhead report 🧳Note: This is a synthetic benchmark with a minimal express app and does not necessarily reflect the real-world performance impact in an application.
|
76f668a to
8d0a14e
Compare
3e95001 to
09dd869
Compare
packages/react/package.json
Outdated
| "@sentry/browser": "10.25.0", | ||
| "@sentry/core": "10.25.0" | ||
| "@sentry/browser": "10.30.0", | ||
| "@sentry/core": "10.30.0", |
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
2b9939c to
1223695
Compare
| "@types/history-4": "npm:@types/[email protected]", | ||
| "@types/history-5": "npm:@types/[email protected]", | ||
| "@types/hoist-non-react-statics": "^3.3.5", | ||
| "@types/node-fetch": "^2.6.11", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Bug: Unrelated @types/node-fetch dependency accidentally added
The @types/node-fetch package was added to devDependencies where @types/hoist-non-react-statics was removed. There's no usage of node-fetch anywhere in the react package, so this appears to be accidentally included during the edit. The dependency is unused and adds unnecessary bloat to the dev dependencies.
size-limit report 📦
|
Ref / Resolves: #18089
hoist-non-react-staticspackage we depend on is not ESM compatible, and causing issues for users on Cloudflare environments. As this package has not been updated in 5 years, and our use has not changed for long time, I think we can just inline this to make it compatible, and save users from explicitly externalizing this package.