github-actions[bot]
commented
7 months ago Would you be able to provide a reproduction? 🙏
Closed maikmetzger closed 5 months ago
github-actions[bot]
commented
7 months ago Would you be able to provide a reproduction? 🙏
maikmetzger
commented
7 months ago Okay, I tested it with a new project. In that it works. I guess something must be odd with the existing one being upgraded. I deleted pnpm-lock.yml and node_modules multiple times, but that isn't it, same error.
danielroe
commented
7 months ago Maybe you have multiple versions of Vue in your project? Would you try running npm why vue?
GhostvOne
commented
7 months ago Since 3.10 I noticed this error too. It's happening totally randomly, i'm not able to make a reproduction
jelmerdemaat
commented
7 months ago I have this same issue when I upgrade from v3.10.3 to v3.11.0. I believe it happens when you have a pages that generates a 500 server error.
ENOENT: no such file or directory, access '/var/folders/wp/p8t.../T/nitro/...' and Nuxt stops working entirely. I have to restart the npm run dev command to get it working again.My system info:
System:
OS: macOS 14.3
CPU: (10) arm64 Apple M1 Pro
Memory: 437.81 MB / 16.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 20.8.1 - ~/.nvm/versions/node/v20.8.1/bin/node
npm: 10.1.0 - ~/.nvm/versions/node/v20.8.1/bin/npm
Browsers:
Chrome: 123.0.6312.59
Safari: 17.3
Safari Technology Preview: 17.4
npmPackages:
@nuxt/devtools: ^1.0.8 => 1.0.8
nuxt: ^3.10.3 => 3.10.3 (this was before the update)
luizzappa
commented
2 weeks ago I faced a similar issue when migrating to Nuxt version 3.13.2. In my case, it started with a maximum call stack size exceeded error because I had a component in the folder structure components/UserPanel/Menu.vue. I was also using PrimeVue, which has a component named Menu as well. I thought my component would be recognized only as UserPanelMenu, but for some reason, the Menu component was also referring to my UserPanelMenu, causing the stack overflow.
To resolve it, I renamed the file from Menu.vue to LateralMenu.vue, which stopped the stack overflow, but then I encountered the error ENOENT: no such file or directory, access.... I tried everything — cleaning the .nuxt, deleting node_modules and package-lock.json, and reinstalling everything, but the error persisted.
What finally worked was renaming the file from LateralMenu.vue to Lateral.vue, and the error disappeared, and everything started working again. I have no idea why this worked, though.
New tests:
I tried changing the file name back to Menu.vue, the stack overflow error came back. However, renaming it to LateralMenu.vue also worked (it was working only with name Lateral.vue). Anyway, I have no idea what happened.
I have the layout:
<template>
<div class="layout-container">
<UserPanelMenu />
<div class="content-container">
<slot />
</div>
</div>
</template>And the components/UserPanel/Menu.vue:
<template>
<!--- other things --->
<Menu /> <!--- PrimeVue Menu. It causes overflow if this file is called Menu too --->
</template>
Environment
Build Modules: -
Reproduction
Unfortunately I cannot upload a repo, due to it being an in-house project for a client. However. I am using Directus and Nuxt, I get data from Directus as usual with a function. I created a test page to replicate the issue.
Normally the .value down in the div can't be read.
Describe the bug
Using Nuxt 3.10.3 I get this error:
Just a 500 error, when removing the content inside div and reloading, it works again.
Doing the same with Nuxt 3.11.0 will cause in a 503 service unavailable and Error: ENOENT: no such file or directory, access '/var/folders/0d...' error. I cannot fix the error and reload the page again. I need to kill pnpm dev and run it again.
{ "statusCode": 404, "statusMessage": "Cannot find any path matching /test.", "stack": [] }
upon first load of the same page. After another reload it will instantly show the ENOENT error and in console:
What I expected: It should throw the regular 500 error page, instead it throws the ENOENT error which won't let me fix the issue and reload the page like it used to be with 3.10.3. Console throws 503 errors in browser then.
If other context is needed, please tell me. I haven't done such reports yet.
Additional context
No response
Logs
No response