Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@EugeneChoi4
Copy link
Contributor

@EugeneChoi4 EugeneChoi4 commented Dec 15, 2025

Upgrading to address node-forge advisory

@react-sizebot
Copy link

Comparing: bcf97c7...3d3db65

Critical size changes

Includes critical production bundles, as well as any change greater than 2%:

Name +/- Base Current +/- gzip Base gzip Current gzip
oss-stable/react-dom/cjs/react-dom.production.js = 6.84 kB 6.84 kB = 1.88 kB 1.88 kB
oss-stable/react-dom/cjs/react-dom-client.production.js = 608.16 kB 608.16 kB = 107.67 kB 107.67 kB
oss-experimental/react-dom/cjs/react-dom.production.js = 6.84 kB 6.84 kB = 1.88 kB 1.88 kB
oss-experimental/react-dom/cjs/react-dom-client.production.js = 667.39 kB 667.39 kB = 117.55 kB 117.55 kB
facebook-www/ReactDOM-prod.classic.js = 693.47 kB 693.47 kB = 122.05 kB 122.05 kB
facebook-www/ReactDOM-prod.modern.js = 683.89 kB 683.89 kB = 120.43 kB 120.43 kB

Significant size changes

Includes any change greater than 0.2%:

(No significant changes)

Generated by 🚫 dangerJS against 3d3db65

Copy link
Member

@rickhanlonii rickhanlonii left a comment

Choose a reason for hiding this comment

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

We should update the deps that use this instead, from yarn why node-forge that looks like webpack-dev-server:

Screenshot 2025-12-15 at 4 38 18 PM

@EugeneChoi4
Copy link
Contributor Author

@rickhanlonii Hm it looks like webpack-dev-server hasn't upgraded their node-forge either (https://github.com/webpack/webpack-dev-server/blob/main/package.json), maybe this is safe to ignore then?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants