The file does not exist at "node_modules/.vite/deps/chunk*" which is in the optimize deps directory.

[someonewithpc]

I'm getting the following message, sometimes, seemingly only after HMR happens a few times:

The file does not exist at "node_modules/.vite/deps/chunk-SZRFMXI5.js?v=f3c2142e" which is in the optimize deps directory. The dependency might be incompatible with the dep optimizer. Try adding it to `optimizeDeps.exclude`.

I haven't been able to find any cause, but as far as I can tell, it didn't result from adding any package, as I haven't done so in a while. It also doesn't happen always, and seemingly only starts happening after HMR, but not after every HMR (HMR as also been really slow)

There's a similar discussion in storybookjs/storybook#28542 but I'm not using storybook

Note: Since I haven't been able to create a minimal reproduction, I can't post this as a bug report

This makes some sense, but I have no idea how I would go about reducing this, tbh...

[efstajas]

Just seemingly randomly started getting the same (with sveltekit). I already completely nuked and reinstalled node_modules. Very strange.

[efstajas]

Clearing cache on the browser fixes it! Strange. Since I've never seen this before and it seems like there is a sudden influx of reports of this recently, I wonder if it's a regression on vite or some other common package.

[efstajas]

I saw the error only locally in dev mode. Another colleague did too, a third didn't (though it might be he was rolling with outdated deps). Prod builds not affected.

Locally, it appeared seemingly on every page I tried to load, and it resulted in a 500 error. So yeah, it caused the page to fail loading.

After clearing the browser cache it's gone and hasn't come back.

[someonewithpc]

For me, cleaning the cache hasn't had an affect, it seems to happen every so often after HMR, causing 500 errors

[videate-miguel]

I got that error after re-installing dependencies in my local environment, and I could fix it by checking the disable cache checkbox on dev tools, I always have that work with that checkbox activate it, but I'm worried that this could translate to our clients, because they will only see a error page or a white screen of death.

[DovMdi]

I get this every time i move a branch, i delete the node_modules and then re-install them.

[Olu-martins]

Clearing cache works, but deleting node modules and npm i seems not to be working.

[yunics-highfield]

Same here. This bug seems to happen when I use dynamic import on local development server. As workaround, I'm trying the 2 ways below. It's gonna happen soon again tho.

1. Reload pages with checking "disable cache" on Network Tab in DevTool.
2. Run npm ci to remove node_modules/.vite and restart vite.

[jimthedev]

Blowing away my node_modules and re-running pnpm i worked for me but this comes back every so often

[Klausdk1999]

Same issue here, removing /node_modules/.vite and npm install solves it until next build or vite --open run

[DaWoelk]

Same issue here. Very annoying.

[jimthedev]

Has anyone stepped back versions to see when it started happening?

[enmanuelmag]

I'm facing the same problem, run npm ci fix the problem but I need to run it always.

[eudoroolivares2016]

We are also running into this issue seemingly at random

[eudoroolivares2016]

Adding this to my vite config seems to help with the issue but, I'm sure I understand the full implications optimizeDeps: { exclude: ['node_modules/.cache'] },

[victor-at-pathpilot]

works for me. Though, would like to understand the details of this.

[hasnainvirk]

Worked for me as well. Please shed some light on the implications.

[tordans]

FYI for others: in my Astro App I don't have a .cache folder, so I could not test this. But the general issue is the same.

[tempura327]

optimizeDeps.exclude
Dependencies to exclude from pre-bundling.

According to the document of Vite, we can use optimizeDeps.exclude to avoid some packages from being pre-building.

So that, if we add optimizeDeps: { exclude: ['node_modules/.cache'] } to vite.config.js, Vite will stop executing pre-building.

When you run Vite for the first time, Vite prebundles your project dependencies before loading your site locally

It means that if you switch to the other branch, and the dependencies between 2 branches are different, Vite will check package.json and node_modules, and judge it it’s necessary to execute pre-building again.

Based on above, followings are my guess.


1. It seems that Vite of some versions don’t execute pre-building when we switch to the other branch, so we get the error. (But I have no idea why the issue don’t happen every time.)
2. If I run command vite optimize --force to execute pre-building manually when I get the error, and the error should be blown away.

I tried run the command, and the error is actually blown away.

To sum up, I supposed the error is related to pre-building. And this is why optimizeDeps: { exclude: ['node_modules/.cache'] } works for this issue.

[TargiX]

I had problems with switching between branches before, so I set

 optimizeDeps: {
    force: true,
  },

but now i see this Chunk issues even with this setting on

[DesiredName]

I also faced the same problem. Vite says it can not find a dependency that is in another project!

[SonnyFishback]

Experiencing the same issue in my SvelteKit app. Resolved by clearing cache and node_modules. Thanks @efstajas

[TargiX]

Same happening randomly when switching between branches with slightly different dependencies

[d-0-t]

Same issue here, it started after upgrading from Angular v17 to 18.2.0, which comes with a new version of Vite I guess.

We work in a monorepo where there is a component library and an app project using the components. Whenever I create a new file that is exported, or change branches without said new files, the bug appears and the web app refuses to load.

Can be temporarily fixed by clearing npm and angular cache, or by disabling caching in the browser. But the moment a file changes, the error comes back.

[t0rbik]

Same issue here. Just started randomly out of nowhere. Deleting node_modules/.vite fixes it for me until it rises again.

UPD: So it happens mostly when I switch branches with different packages installed. Most of the time vite says: Re-optimizing dependencies because lockfile has changed. But when it doesn't see changed lockfile for whatever reason, I end up with the error in question. So I'm trying to workaround with the following now:

  optimizeDeps: {
    force: true,
  },

[TargiX]

I remember times when I was able to run my webpack project in 30-40 seconds and start working right away. Now it looks like it build in seconds but in reality i'm sitting and waiting for minutes constantly waiting for deps optimize/reoptimize and actully see my app loaded. Starting questioning myself why i'm moved away from webpack?

[ottopaulsen]

I have seen this many times lately, after lots of dependency updates.
When I add this to vite.config.js, it helps for a while:

  optimizeDeps: {
    exclude: ["node_modules/.vite"],
  },

but then after some times it comes again, and then I just change to

  optimizeDeps: {
    exclude: [".vite"],
  },

and restart the dev-server, and then it is ok again.
That is the fastest and simplest workaround I have found so far.

[Melek-E]

This is still happening, so far clearing the browser cache fixes it immediately?

[aardhyn]

Same issue. I updated a large number of dependencies and this problem started happening each time I restarted the dev server. Reloading with "disable cache" has fixed the problem for me.

[adriandmitroca]

I just started getting this today out of nowhere, without touching anything in my lock file. It's now happening literally every few minutes, the only way to fix this is wiping out node_modules and doing the install again. That's nuts.

[addy]

We are currently experiencing this with vite 5.4.5

[daniel-stclair]

This happens to me every time I restart my app after switching branches. It's become quite the headache.