3.0.0-rc.10
Node 8.9.4 / yarn 1.7.0 / Windows 10
If you have more than 5 page entries, vue-cli will remain in the building state without displaying the compilation results.
Such as this in your vue.config.js:
module.exports = {
pages: {
index1: 'src/index1.js',
index2: 'src/index2.js',
index3: 'src/index3.js',
index4: 'src/index4.js',
index5: 'src/index5.js',
index6: 'src/index6.js',
},
}
Each of index*.js has similar code, such as
import Vue from 'vue'
import App from './Test.vue'
Vue.config.productionTip = false
new Vue({
render: h => h(App),
}).$mount('#app')
// Test.vue
<template>
<div class="test">
<h1>This is an testpage</h1>
</div>
</template>
Continue to compile...
It will remain in the building state without displaying the compilation results
I did the same test on my mac and I encountered the same problem.
Node 8.11.2 / yarn 1.7.0 / Mac 10.13.6
Please provide an actual repository with the code you describe. We don't do manual reproductions.
code.zip
like this ... @LinusBorg
A github repository would be easier, but a zip might do
Ok, next time I will... But can you reproduce my problem?
I think this may be a webpack issue, or a combination of multiple html-webpack-plugins...
@yyx990803 You are right, it seems to be the webpack's bug...
I remember that I was able to use it normally in the beta.15 version, so I checked the dependency of @vue/cli-service (mainly webpack & html-webpack-plugins), you used [email protected] in rc3, then you switch to [email protected]. This is the cause of this problem ...
When I switch back to the rc3 version, the above build is working fine.
Figured out how to switch to rc3 and worked for me too!
What I did was deleted node_modules folder and package-lock.json, removed @vue/cli-plugin-babel, @vue/cli-plugin-eslint and @vue/cli-service from package.json and installed rc3 version for those 3 packages (npm install @vue/[email protected])
It's a regression introduced in https://github.com/vuejs/vue-cli/commit/4b5a63441b385d5d7f9b92cf5ed4d61d4eae39c9
For now, a workaround is to disable named-chunks plugin in vue.config.js:
module.exports = {
// ...
chainWebpack: config => config.plugins.delete('named-chunks')
}
Most helpful comment
For now, a workaround is to disable
named-chunksplugin invue.config.js: