Florian
Florian
Hey Daniel. If you delete the `.nuxt` folder with Nuxt 3.20.x while the dev server is running you cannot see a error? By me the error occurs on WSL +...
The problem might be in `pages/runtime/page.ts`: My understanding is that the original logic assumed: !hasSameChildren means "we're going to a lower route, so there was nothing here before." But that's...
Hey. I guess `photoswipe` or other libs are loading bit faster and comes into the `vite.optimizeDeps.exclude` array as well. But this process runs asynchronous. I tried to check the excluded...
use node `22.20` then the problem should be gone.
Ok... Is it possible for you to try it with `pnpm`? It should work always, absolutly. But there is really a bug in npm. If `pnpm` throw the same error...
Ok... I tried it on Linux Ubuntu 24.x with npm and pnpm, and under Windows with npm `11.6.2` I can#t reproduce the error with your repo. I think you tried...
Because it's mostly an `npm` issue: ``` ERROR Cannot find native binding. npm has a bug related to optional dependencies (https://github.com/npm/cli/issues/4828). Please try npm i again after removing both package-lock.json...
A lilttle more infos, please @plcdnl :-) Do you use `node 22.20` + `pnpm 10.18 (or higher)` ?
I think it's similar problem here: #33120 But I think the way to go should be npm 9. What the problem with pnpm in Coolify is, I don't know. But...
I think there are some ways... First - package.json - set package manager: ```json { "packageManager": "[email protected]" // or: "[email protected]", "yarn@...", } ``` Second for Node: `.nvmrc` ``` v22 ```...