Replies: 1 comment
-
I'm experiencing a similar issue when upgrading from Gatsby 3 to Gatsby 4. Is there anything in the build process that has changed? Our page speed scores were negatively impacted due to increase in bundle size. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have site on gatsby after update gatsby from 3v to 4v bundle structure changed. I followed the instruction - https://www.gatsbyjs.com/docs/reference/release-notes/migrating-from-v3-to-v4/.
Before was this
And after update I got this
Then I added webpack configs
config.optimization.splitChunks = { chunks: 'all', name: false, cacheGroups: { vendors: { test: /[\\/]node_modules[\\/]/, reuseExistingChunk: true, }, commons: { minChunks: 2, reuseExistingChunk: true, }, }, };
and the result was
I was able to achieve almost the same result using React.lazy but had problems with css loads
Can I get the same chunks with gatsby 4 as I got with 3rd version? (without lazy load)
Beta Was this translation helpful? Give feedback.
All reactions