Vue.js stuck on serving at 40% how to recover?

98% after emitting copyplugin
vue cli
vue cli build slow
npm run build stuck
vue-cli-service
vue build hang
vue cli service build hang
npx vue cli

I decided to delete the node modules folder, do a npm install then do a npm run serve it always gets stuck around 40% and stays there forever. When done from the UI it also gets stuck on a similar amount:

$ vue-cli-service serve --open --mode development --https --dashboard INFO Starting development server...

40% building 118/134 modules 16 active ...tApp\node_modules\axios\lib\defaults.js

another time:

40% building 134/147 modules 13 active ...\node_modules\axios\lib\adapters\xhr.js

I notice Node.js process is constantly going at around 15%, but nothing happens if I wait and wait and wait.

Package.json
{
  "name": "myapp",
  "version": "0.1.0",
  "private": true,
  "scripts": {
    "serve": "vue-cli-service serve",
    "build": "vue-cli-service build",
    "lint": "vue-cli-service lint",
    "test:e2e": "vue-cli-service test:e2e",
    "test:unit": "vue-cli-service test:unit"
  },
  "dependencies": {
    "@aspnet/signalr": "^1.1.4",
    "axios": "^0.18.0",
    "vue": "^2.6.10",
    "vue-axios": "^2.1.4",
    "vue-router": "^3.0.6",
    "vuex": "^3.1.1"
  },
  "devDependencies": {
    "@vue/cli-plugin-babel": "^3.7.0",
    "@vue/cli-plugin-e2e-cypress": "^3.7.0",
    "@vue/cli-plugin-eslint": "^3.7.0",
    "@vue/cli-plugin-unit-jest": "^3.7.0",
    "@vue/cli-service": "^3.7.0",
    "@vue/eslint-config-standard": "^4.0.0",
    "@vue/test-utils": "^1.0.0-beta.20",
    "babel-core": "7.0.0-bridge.0",
    "babel-eslint": "^10.0.1",
    "babel-jest": "^23.6.0",
    "eslint": "^5.16.0",
    "eslint-plugin-vue": "^5.2.2",
    "node-sass": "^4.12.0",
    "sass-loader": "^7.1.0",
    "vue-template-compiler": "^2.6.10"
  },
  "eslintConfig": {
    "root": true,
    "env": {
      "node": true
    },
    "extends": [
      "plugin:vue/essential",
      "@vue/standard"
    ],
    "rules": {
      "space-before-function-paren": [
        "error",
        {
          "anonymous": "always",
          "named": "always",
          "asyncArrow": "always"
        }
      ],
      "keyword-spacing": [
        "error",
        {
          "after": true
        }
      ],
      "semi": [
        "error",
        "always"
      ],
      "indent": "off",
      "vue/script-indent": [
        "warn",
        2,
        {
          "baseIndent": 1
        }
      ]
    },
    "parserOptions": {
      "parser": "babel-eslint"
    }
  },
  "postcss": {
    "plugins": {
      "autoprefixer": {}
    }
  },
  "browserslist": [
    "> 1%",
    "last 2 versions",
    "not ie <= 8"
  ],
  "jest": {
    "moduleFileExtensions": [
      "js",
      "jsx",
      "json",
      "vue"
    ],
    "transform": {
      "^.+\\.vue$": "vue-jest",
      ".+\\.(css|styl|less|sass|scss|svg|png|jpg|ttf|woff|woff2)$": "jest-transform-stub",
      "^.+\\.jsx?$": "babel-jest"
    },
    "moduleNameMapper": {
      "^@/(.*)$": "<rootDir>/src/$1"
    },
    "snapshotSerializers": [
      "jest-serializer-vue"
    ],
    "testMatch": [
      "**/tests/unit/**/*.spec.(js|jsx|ts|tsx)|**/__tests__/*.(js|jsx|ts|tsx)"
    ],
    "testURL": "http://localhost/"
  }
}

$ node --version v10.15.3

How do I recover from this?

Update: There is something magic about the number 40, I removed all mentions of Axios and now I still get stuck at 40% but with a different thing:

40% building 133/146 modules 13 active ...abel\runtime-corejs2\core-js\promise.js

In my case:

It was an error into the template. Make sure there is a container tag just after <template><container_tag> ... your code ...</container_tag></template> it could be as simple as a <div>

Vue-Cli 3, pages: 'npn run build' gets stuck - Get Help, I'm using the pages setting in my vue.config.js. It looks something like this: module.exports = { baseUrl: process.env.NODE_ENV� Teams. Q&A for Work. Stack Overflow for Teams is a private, secure spot for you and your coworkers to find and share information. Learn more

    // vue.config.js
    module.exports = {
      chainWebpack: (config) => {
        config.resolve.symlinks(false)
      }
    }

Link: https://cli.vuejs.org/guide/troubleshooting.html#running-installation-enter code herewith-sudo-or-as-root

core-js module error � Issue #3678 � vuejs/vue-cli � GitHub, Version 3.5.1 Environment info mac os 10.14.3 Steps to reproduce vue-cli- service serve --mode development What is expected? run the project� Teams. Q&A for Work. Stack Overflow for Teams is a private, secure spot for you and your coworkers to find and share information. Learn more

This seems to be caused by an error in one of your project files which prevents compilation and also compresses any error message.

I was personally bothered by this today, and spent a lot of time unnecessarily debugging WSL before finding the error in one of my components.

Try to comment out or remove any components, in templates, component registrations and imports, until it starts loading again.

Vue js, Vuetify npm run serve gets hang on 40% while building and , Vue js, Vuetify npm run serve gets hang on 40% while building and it can't building anymore it get stuck 40% without throwing anything as a� Oh my God! It is not that much complicated, with these answers which also works. However, other answers tho this question also works well. If you really want to use the vue-cli-service and if you want to have the port setting in your package.json file, which your 'vue create <app-name>' command basically creates, you can use the following configuration:

Check all your components for merge conflicts. If you're using vscode, try to search for the string >>>>> on your project folder.

It worked for me!

node.js - Vue.js坚持以40%的投放率进行恢复?, 我决定删除节点模块文件夹,进行npm install然后进行npm run serve因为它始终卡在左右并 Vue.js stuck on serving at 40% how to recover? You might get stuck. But I’m here to help. There’s nothing worse than getting five hours into a course, getting stuck, and not getting the help you need to continue. I’m in the Q&A everyday to help you get unstuck. I reply to every question to get you back on track. Don’t take my word for it.

I ran a linter as a step before serve and noticed that it corrected one of the files. It still didn't run. But I decided to go through the file and noticed that there was one closing tag missing.

It will be tedious, but look through your components to see whether you have a missing closing tag.

I also found that checking the first place the numbers pause and using that as a way to narrow down the file with a problem helped me sort it out faster.

40% building 223/268 modules 45 active ...rders\List.vue?

Vue Mastery, However, a full-featured Vue 2 project with Vuex + vue-router included (~30kb tags representing the start and finish of each lesson, just in case you get stuck. If needed, use the self-help links here to reset your username or password. It serves as a centralized store for all the components in an application, with rules� 40. A study on the history of indexing in India. A study on indexing extends to a wide arena of the process of publication, citation, information retrieval, information storage, and knowledge management as a whole. The following research is inspired by the culture & practice of valuing knowledge in India.

Demystifying the v-model Directive in Vue, Learn about the v-model directive in Vue.js, and get to know the basics of The problem with this approach is that you are stuck having to then add Now do this 40 times for a big form, please. When you visit any web site, it may store or retrieve information on your browser, mostly in the form of cookies. Try Vue.js! Build cool things in no time, during the 45 minutes session we take an comprehensive overview over Vue.js. From installation, configuration, components over the template syntax.

Getting up and Running with the Vue.js 2.0 Framework, Jack Franklin tries out Vue.js 2.0, and walks through building a basic GitHub API demo to babel-loader vue-loader vue-template-compiler webpack-dev-server of using the variable name vm for Vue applications has stuck. But when we do extract it, it will be fully-formed and ready for consumers since it’ll already have been serving the demanding needs of FOG. Fourth, we have tests. This was a bit of a struggle as the build order of Firefox means that any Rust code we write that touches Firefox internals can’t be tested in Rust tests (they must be tested by

Laravel Rfid, As of now a large portion of the foundations requests that understudies create PHP HTML5 Canvas JavaScript Course Icon Angular React Vue Jest Mocha NPM for Radio Frequency Identification and is used to store and retrieve information. I want to send json object to my directive but I got stuck with below code,�

Comments
  • Try to uninstall and reinstall vue-cli?
  • Did you find the answer ? I've same problem than you
  • You saved the day. Was going crazy with not seeing any error if Templates are not done right. Thanks.
  • saved my day...