vue-cli: vue-cli-service build hangs indefinitely
Version
4.5.6
Environment info
System:
OS: Linux 3.10 CentOS Linux 7 (Core)
CPU: (2) x64 Intel(R) Xeon(R) CPU E5-2686 v4 @ 2.30GHz
Binaries:
Node: 12.18.4 - /bin/node
Yarn: Not Found
npm: 6.14.8 - /bin/npm
Browsers:
Chrome: 85.0.4183.102
Firefox: 68.12.0esr
npmGlobalPackages:
@vue/cli: 4.5.6
Steps to reproduce
I have a Vue project in Node that I am trying to build via ‘npm run build’. This works fine using the latest NPM (v6.14.8). Using the npm (v6.14.4) shipped with GraalVM causes it to hang indefinitely. FWIW my Vue project is built in Node and compiled using ES4x for Vert.x. I have tried the same with a prior GraalVM build (19.2.1) and get the same error. I am using v4.5.6 of the vue-cli-service package.
package.json snippet:
"scripts": {
"serve": "vue-cli-service serve",
"build": "vue-cli-service build",
"lint": "vue-cli-service lint",
"postinstall": "es4x install",
"start": "es4x",
},
Ex:
> which npm
/bin/npm
> npm -v
6.14.8
> npm run build
> vue-cli-service build
⠴ Building for production...
...Lots of output followed by...
DONE Build complete. The dist directory is ready to be deployed.
> /path/to/graalvm-ce-java8-20.2.0/bin/npm run build
> vue-cli-service build
⠴ Building for production...
<I never get any further output from this. It hangs on the last line shown above>
What is expected?
For the call to complete
What is actually happening?
The call does not complete
About this issue
- Original URL
- State: open
- Created 4 years ago
- Comments: 20 (3 by maintainers)
I upgraded to node 20 for that part of my build and it’s working; there is something about node 18 which is causing the issue in my case
Running the build command on docker makes the process hang for me too and I’m not using GRAALVM.
For my case, build process ended with node v14 but non-stop with node v16 & v18.
I’m suddenly seeing this as well, using node v18 and the latest vue-cli-server 4.x / vue 2.7
I can try building using node 14, I suppose, see if that helps…
If anyone finds a way to get useful debug info out of the process please share! setting env var “NODE=*” gets a lot of extra debug stuff printed, but it still hits a point where it just stalls indefinitely with no explanation
hi,I have same problem ,did you solve the problem