murshex

Press "Test Navigate" button and you will see the page refresh instead of bringing you to the route. Click it a 2nd time and it will correctly bring you to...

Ok I have more info, @danielroe [recommendation](https://github.com/nuxt/nuxt/issues/27544#issuecomment-2168194904) is one way to allow vee-validate to work with PNPM. But its actually what is causing the `optimized dependencies changed. reloading`. Manually installing...

Ah, found another workaround. Creating `.npmrc` with `shamefully-hoist=true` also allows PNPM to work with vee-validate. No need to add anything to your `nuxt.config.ts` or manually install `@vue/devtools-api`. So I guess...

> There is this workaround: [#26783 (comment)](https://github.com/nuxt/nuxt/issues/26783#issuecomment-2058966800) No thanks. That workaround is unmanageable

Best solution that I have for now is adding `public-hoist-pattern[]=@vue/devtools-api` to `.npmrc`

> > > There is this workaround: [#26783 (comment)](https://github.com/nuxt/nuxt/issues/26783#issuecomment-2058966800) > > > > > > No thanks. That workaround is unmanageable > > I it annoying yes, but pretty straight...

Lastly, I would prefer if primevue didn't cause `optimized dependencies changed. reloading`, I don't understand why this is necessary. I think someone ought to take a look at that too....

> You don't add the components to the list, but the affected libraries. Unless you add third party dependencies every day, this workaround is not too bad. You're simply just...

> Any idea for a better workaround for this issue? adding `public-hoist-pattern[]=@vue/devtools-api` to .npmrc

+1