Vite optimized dependencies changed and reloading many times

[whitedwarf2000]

Hello everyone,

I'm encountering an issue when trying to start my monorepo project using the package manager pnpm.
Surprisingly, Vite repeatedly refreshes due to changes in optimized dependencies, as depicted in the attached screenshot below:

I've attempted various solutions, including:

• Executing the command pnpm vite --force
• Adding lodash (and some other libraries that I suspected might be causing the frequent reloads) to optimizeDeps.include (I also tried the exclude option, but the problem persisted).
• Follow some advice from the relevant thread: Glob support in optimizeDeps.include #5419

Unfortunately, none of these methods have resolved the issue. Would anyone be able to provide some guidance on this matter?

Thank you.

My system:

• vite: 4.4.9
• pnpm: 8.9.2
• os: macOS Ventura 13.5

My vite.config.ts:

[sadn1ck]

Hmm, if possible try switching to lodash-es and even then if it persists try adding lodash-es to optimizeDeps.exclude

[whitedwarf2000]

Hi @sadn1ck , thanks for answering,

My project was using lodash/fp (more than 4k lines of code), so replacing lodash/fp with lodash-es was unable to do at the moment. I workaround by changing the package.json (without changing vite.config.ts ) like this:

Before:

After:

then, I ran pnpm install and pnpm vite --force again, and this is the result:

It seems vite can't find the direct path to node_modules even though I can navigate inside my IDE
Do you have any ideas?

[sadn1ck]

Can you share a minimal reproduction?

Can you confirm if you can have lodash/fp in package.json deps? I think you cannot (have the / when package name is not scoped)

• try changing lodash/fp to lodash-fp in package.json (also types)
• run an npm i
• change import to import {get} from 'lodash-fp' since AFAIK you can do a named import from lodash-es

[whitedwarf2000]

Hi, I attempted the following steps to address the issue above:

• ran pnpm store prune (to removes unreferenced packages from the store)
• removed node_modules (outside package and monorepo packages)
• ran pnpm install --shamefully-hoist (creates a flat node_modules structure)
• ran pnpm vite --force (start my application)

Following these steps seemed to resolve the issue (though I can't confirm with absolute certainty now). I share these steps hoping they assist others facing a similar problem.

[dan-wellman-cs]

I don't think this is specific to a particular framework/library/setup/platform.

We recently upgraded to Vite 5.4.11 (no other changes) in a large Vue3 app and started seeing this issue also. We see messages about Lodash as well, but also other 3rd-party libs like AG-Grid, Vue-multiselect, and fuse.js.

It's incredibly annoying, and happens frequently during development locally. Can't the reloading be disabled somehow?

[dan-wellman-cs]

FWIW, we discovered that some legacy code in the app was trying to load a dependency which no longer existed. Once this issue was fixed, this constant reoptimizing and reloading of dependencies vanished.

[artemis-prime]

I'm still seeing this. Why is this closed??

[go-aegian]

Have several dev dependencies and at the beginning of running dev it takes a while to re-optimize dependencies each time I need to run debug/dev mode.

I concur with you not sure why it has been closed without mentioning possible solutions or if this will be taken care by vite somehow

It's very annoying and not helpful to constantly keep reoptimizing even when the dependencies versions remains the same for a long time.

[whitedwarf2000]

Hi,
apologies for closing this discussion earlier without providing an explanation.

As this issue has remained unresolved for quite some time, I decided to take a different approach in my project. Instead of migrating to pnpm, I upgraded Yarn to a newer version.

I've reopened this discussion so that others who are experiencing the same issue can collaborate, and we can work together to find a solution.

[go-aegian]

Thanks for reopening it, I'm still having the problem and on my end I use npm if that helps

[vanics]

Alo seeing this

[vladinator1000]

This is driving me insane, constant reoptimizing of dependencies causes Cloudflare's workerd to crash when using @cloudflare/vite-plugin

workerd/jsg/setup.c++:39: fatal: V8 fatal error; location = Reached heap limit; message = : allocation failed: JavaScript heap out of memory

[SlexAxton]

Also running into this. Using pnpm as well. My project is nascent though, and has very few dependencies. It means that every time I load my app in dev for the first time, it shows an error, and then it works on a reload.

[NeroZonbolt]

I use npm run dev and it happens as well, I use Nuxt + Vite and I'm getting this stuff happening... It's unbearable what am I supposed to do to avoid that

[mindplay-dk]

plain NPM here as well, latest version of Vite... happens all the time... very annoying. 😌

[blixt]

Yeah this on-demand optimization might seem like a smart way to speed up runtime of a project, but not when Vite just reloads randomly without question, throwing away built-up user state forcing the user to start over. I'd much rather have a 10 second "please wait" screen than this. Can it be configured?

[arnab-trameter]

Facing the same issue in my React Project.

React: v19.1.0
Vite: 6.3.5
React Router: 7.6.1
Shadcn & RadixUI.

1:56:39 PM [vite] (client) ✨ new dependencies optimized: next-themes, sonner, jotai, jotai/utils, axios, date-fns-tz, date-fns, react-icons/io5, react-icons/hi, react-icons/hi2, @radix-ui/react-popover, react-icons/fa, @radix-ui/react-slot, class-variance-authority, react-hook-form, @hookform/resolvers/zod, zod, clsx, tailwind-merge, react-calendar
1:56:39 PM [vite] (client) ✨ optimized dependencies changed. reloading
1:58:42 PM [vite] (client) ✨ new dependencies optimized: react-phone-number-input/input, lucide-react, @radix-ui/react-label, @radix-ui/react-alert-dialog, @radix-ui/react-toggle-group, @radix-ui/react-accordion, react-day-picker, @radix-ui/react-toggle
1:58:42 PM [vite] (client) ✨ optimized dependencies changed. reloading

[mindplay-dk]

It's not clear to me why it needs to detect new dependencies on-the-fly in the first place?

Wouldn't it make more sense to watch the file system and immediately optimize new dependencies after they get installed?