What is _next/static/chunks/framework.*******.js?

[deependras1110]

Is this some static file?

[icyJoseph]

That's the react core and the react-dom library packaged to be sent to the client, both minified, uglyfied and optimised for production.

[deependras1110]

So one of the errors I get after deploying the next.js app on production is this framework.js missing along with webpack.js
So is it the issue with the dependencies, version of react?

[icyJoseph]

With this much information the issue could be anything really.

When next.js does the build it compiles this files iirc. I'm not sure what the actual pipeline looks like, but these end up in the .next folder.

I really don't think this has anything to do with next.js or react, rather this ought to be a pipeline error. The question we must answer is, why are these missing?

If you build locally, can you see them? What does the production deploy do? Are you using a custom webpack config?

[deependras1110]

I inspected the application locally, and I can see the webpack.js but not framework.js under Network. However, I am not sure if the application needs to fetch framework.js in local since it's for packaged content into production.
As far as the custom webpack, yes have custome webpack config

Also, the project with next.js v9 is working fine when in prod, but upgrading to next.js v12, the prod is breaking.

[icyJoseph]

I inspected the application locally, and I can see the webpack.js but not framework.js under Network.

You should see the structure of .next and see if it's there, at the .next/_next/static/chunks/framework.[hash].js location.

However, I am not sure if the application needs to fetch framework.js in local since it's for packaged content into production.

What do you mean here? If you build the application and run it, locally, in a server, the client will still request the framework because the script is part of the initial HTML

As far as the custom webpack, yes have custome webpack config
Also, the project with next.js v9 is working fine when in prod, but upgrading to next.js v12, the prod is breaking.

I see, this was good to know. Could it be that there's some issue with the file hashing? What plugins or what does the custom webpack config do? From Next.js v9 to v12, WebPack 5 became enforced, so there might definitely be some breaking changes there, brought by webpack v5.

[isayanotud]

/next/static/chunks/16fce0~0kfr7.js

[Karen86Tonoyan]

https://github-karentonoyan-pl.lovable.app

[xNastouills]

Hi

_next/static/chunks/framework.*******.js is the chunk that packages React and React-DOM core libraries. In production, Next.js minifies and optimizes these core dependencies into this dedicated static chunk so it can be served to the client.

If you are getting missing/404 errors on this file in production after upgrading (e.g., Next.js 9 to 12+), it is usually caused by:

Custom Webpack configuration issues: Next.js switched to Webpack 5, which can break custom Webpack plugins or chunking logic from older versions.

Build vs. Deployment mismatch: Static chunks are generated with a unique content hash during next build. If your server restarts, redeploys, or uses multiple instances without persistent deployment assets, the client might request an older/missing hash.

[TomT15]

Just for clarification since im doing similar research.

My understanding is that React provides the underlying library code, while the bundler/build system determines how that code is compiled, split into chunks, optimized, and ultimately served. This would also explain why applications built with Vite, Webpack, or different Next.js versions may package React differently.

Is that understanding correct?