Vue 3 + Vite run into error on build. Error: EINVAL: invalid argument, realpath #9227
Unanswered
Toge360
asked this question in
Help/Questions
Replies: 1 comment 1 reply
-
Without providing a minimum stable code repository that reproduces the problem, it will be difficult for us to locate the problem. I recommend that you provide it. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
We have a problem in our NodeJS environment on the servers of ProfiHost (German provider) using Vite in a Vue 3 app.
Installing the deps via npm i works fine.
However, the build via npm run generate always runs with the following error:
[1:11:34 PM] ERROR Nuxt Build Error: EINVAL: invalid argument, realpath '/home/user/gitroot/ourapp/node_modules/nuxt/dist/app/entry.js' at realpathSync.native (node:fs:2644:3) at getRealPath (node_modules/vite/dist/node/chunks/dep-df561101.js:28826:20) at tryCleanFsResolve (node_modules/vite/dist/node/chunks/dep-df561101.js:28307:16) at tryFsResolve (node_modules/vite/dist/node/chunks/dep-df561101.js:28296:17) at Object.resolveId (node_modules/vite/dist/node/chunks/dep-df561101.js:28152:24) at node_modules/rollup/dist/es/shared/node-entry.js:25539:40 at async PluginDriver.hookFirstAndGetPlugin (node_modules/rollup/dist/es/shared/node-entry.js:25439:28) at async resolveId (node_modules/rollup/dist/es/shared/node-entry.js:24112:26) at async ModuleLoader.resolveId (node_modules/rollup/dist/es/shared/node-entry.js:24526:15) at async Object.resolveId (node_modules/vite/dist/node/chunks/dep-df561101.js:7910:10)
At first I assumed that it was due to the realpth plugin, which is not available. According to the provider, realpath is available everywhere.
The following test shows that realpath is available:
Provider-Quotes:
The error must be somewhere else, unfortunately we can't do anything more than provide the command.
I tried to find the solution to the problem, unfortunately in vain.
The assumption is that it is a software problem.
In addition, the process ran error-free until an update was carried out by the provider. In my opinion it must be up to the provider.
The same error also occurs in a Nuxt 3 + Vite installation.
Can someone give me a hint as to what exactly the problem could be?
Which option have we and the provider overlooked so far?
I'm happy about feedback!
Greetings,
Tobi
Beta Was this translation helpful? Give feedback.
All reactions