You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What you're doing and what's happening: Trying to build a node Vue app for production.
What's wrong / what should be happening instead: It should build the app. Instead, build runs forever.
From a clean install of Ubuntu/WSL,
Install nvm, node v8, and @vue/cli
node -v : 8.11.3 (problem also happens with v9 and v10, btw)
npm -v: 5.6.0
vue -V : 3.0.0-rc.3
use vue create to create a sample app with defaults.
npm run build to build the project for production
Observe that the build never finished, and a node process is consuming 100% of a core.
What appears to be happening is, within the running of webpack as part of the compile, a call from native back to node for managing async callbacks/promises isn't doing anything. In particular, in async_hooks.js, the function emitHookFactory will be called over and over again with the same asyncId, but for that particular asyncId it does not do anything -- seemingly leaving it on the list of callbacks yet to be resolved. Rinse and repeat.
This behavior is not observed on CentOS (in a Hyper-V VM) with the exact same project and same versions of node/npm/vue.
The text was updated successfully, but these errors were encountered:
Your Windows build number: 10.0.17692.1004
What you're doing and what's happening: Trying to build a node Vue app for production.
What's wrong / what should be happening instead: It should build the app. Instead, build runs forever.
From a clean install of Ubuntu/WSL,
Install nvm, node v8, and @vue/cli
node -v : 8.11.3 (problem also happens with v9 and v10, btw)
npm -v: 5.6.0
vue -V : 3.0.0-rc.3
use
vue create
to create a sample app with defaults.npm run build
to build the project for productionObserve that the build never finished, and a node process is consuming 100% of a core.
What appears to be happening is, within the running of webpack as part of the compile, a call from native back to node for managing async callbacks/promises isn't doing anything. In particular, in
async_hooks.js
, the functionemitHookFactory
will be called over and over again with the sameasyncId
, but for that particularasyncId
it does not do anything -- seemingly leaving it on the list of callbacks yet to be resolved. Rinse and repeat.This behavior is not observed on CentOS (in a Hyper-V VM) with the exact same project and same versions of node/npm/vue.
The text was updated successfully, but these errors were encountered: