Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

vue-cli will remain in the building state without displaying the compilation results when you have more than 5 page entries(in my computer) #1996

Closed
crown3 opened this issue Jul 31, 2018 · 10 comments · Fixed by #2324

Comments

@crown3
Copy link

crown3 commented Jul 31, 2018

Version

3.0.0-rc.10

Node and OS info

Node 8.9.4 / yarn 1.7.0 / Windows 10

Steps to reproduce

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>

What is expected?

Continue to compile...

What is actually happening?

It will remain in the building state without displaying the compilation results

@crown3
Copy link
Author

crown3 commented Jul 31, 2018

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

@LinusBorg LinusBorg added the needs reproduction This issue is missing a minimal runnable reproduction, provided by the author label Jul 31, 2018
@LinusBorg
Copy link
Member

Please provide an actual repository with the code you describe. We don't do manual reproductions.

@crown3
Copy link
Author

crown3 commented Jul 31, 2018

code.zip
like this ... @LinusBorg

@LinusBorg
Copy link
Member

A github repository would be easier, but a zip might do

@crown3
Copy link
Author

crown3 commented Jul 31, 2018

Ok, next time I will... But can you reproduce my problem?

@yyx990803 yyx990803 added bug scope: cli-service build and removed needs reproduction This issue is missing a minimal runnable reproduction, provided by the author labels Jul 31, 2018
@yyx990803
Copy link
Member

I think this may be a webpack issue, or a combination of multiple html-webpack-plugins...

@crown3
Copy link
Author

crown3 commented Aug 1, 2018

@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 webpack@4.8.2 in rc3, then you switch to webpack@4.15.1. This is the cause of this problem ...
When I switch back to the rc3 version, the above build is working fine.

@murilobd
Copy link

murilobd commented Aug 21, 2018

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/cli-service@v3.0.0-rc.3)

@haoqunjiang
Copy link
Member

It's a regression introduced in 4b5a634

@haoqunjiang
Copy link
Member

For now, a workaround is to disable named-chunks plugin in vue.config.js:

module.exports = {
  // ...
  chainWebpack: config => config.plugins.delete('named-chunks')
}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants