profile
viewpoint
vue-bot vue-bot @vuejs Internet cloud Hi! I'm your [robot-friend]. Bip blop!

issue closedvuejs/vue

The Vue.js does not execute the command despite the correct encoding

I do not really understand what is wrong with this code I think it is a good code and there are no errors, but despite that it does not execute orders as required Please find a solution to this matter var app = new Vue({ el: '#daniel-app', data: { inPut: '', outPut: '', buttonText: 'fab fa-telegram-plane', clarification: 'Convert the title to Slug' }, methods: { convertToSlug () { var theSlug = this.inPut; // [1] Convert the post title to lowercase theSlug = theSlug.toLowerCase(); // [2] Replace spaces with a dash theSlug = theSlug.replace(/\s+/g, '-'); // [3] Replace ampersand with a dash theSlug = theSlug.replace(/&/g, '-'); // [4] Replace 2 dashs with nothing theSlug = theSlug.replace(/--/g, ''); // [5] Delete a dash in end and first post title var firstDash = theSlug.charAt(0); var endDash = theSlug.charAt(theSlug.length - 1); if (firstDash === '-' && endDash === '-') { theSlug = theSlug.replace(firstDash, ''); theSlug = theSlug.replace(endDash, ''); } else if (firstDash === '-') { theSlug = theSlug.replace(firstDash, ''); } else if (endDash === '-') { theSlug = theSlug.replace(endDash, ''); } // Add result post title to output if (this.outPut === theSlug) { this.outPut = ''; this.buttonText = 'fab fa-telegram-plane'; this.clarification = 'Convert the title to Slug'; } else if (this.buttonText === 'fas fa-times') { this.outPut = ''; this.buttonText = 'fab fa-telegram-plane'; this.clarification = 'Convert the title to Slug'; } else { this.outPut = theSlug; this.buttonText = 'fas fa-times'; this.clarification = 'Delete this slug'; console.log(endDash); } } } });

Preview: https://danieleg.000webhostapp.com/vue/vue/slug.html

closed time in an hour

daniel-EG

issue commentvuejs/vue

The Vue.js does not execute the command despite the correct encoding

Hello, thank you for taking time filling this issue!

However, we kindly ask you to use our Issue Helper when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatically closed by me (your robot friend!).

I hope to see your helper-created issue very soon!

daniel-EG

comment created time in an hour

issue closedvuejs/vue

rollup-plugin-alias is currently archived and it's not currently in dev

I'm currently started learning Vue, I found that documentation its really helpful, I clone this repo and trying to start learning each in-depth modules that vue-team has created. I tested each module's like compiler , core , platform and server and i'm trying learn more about each of your modules..

I found this rollup-plugin-alias looks like this is archived and moved to @rollup/plugin-alias and its uses the same func that config.js is using in /scripts

can i fix this .... ;) Thanks 🎉

closed time in 2 hours

Usamaliaquat123

issue commentvuejs/vue

rollup-plugin-alias is currently archived and it's not currently in dev

Hello, thank you for taking time filling this issue!

However, we kindly ask you to use our Issue Helper when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatically closed by me (your robot friend!).

I hope to see your helper-created issue very soon!

Usamaliaquat123

comment created time in 2 hours

issue closedvuejs/vue-cli

multi-page配置删除preload插件无法注入vendors文件

Version

4.2.0

Environment info

System:
    OS: macOS Mojave 10.14.2
    CPU: (4) x64 Intel(R) Core(TM) i7-7567U CPU @ 3.50GHz
  Binaries:
    Node: 12.2.0 - ~/.nvm/versions/node/v12.2.0/bin/node
    Yarn: 1.22.0 - /usr/local/bin/yarn
    npm: 6.9.0 - ~/.nvm/versions/node/v12.2.0/bin/npm
  Browsers:
    Chrome: 80.0.3987.122
    Firefox: 68.0.1
    Safari: 12.0.2
  npmPackages:
    @vue/babel-helper-vue-jsx-merge-props:  1.0.0 
    @vue/babel-plugin-transform-vue-jsx:  1.1.2 
    @vue/babel-preset-app:  4.2.2 
    @vue/babel-preset-jsx:  1.1.2 
    @vue/babel-sugar-functional-vue:  1.1.2 
    @vue/babel-sugar-inject-h:  1.1.2 
    @vue/babel-sugar-v-model:  1.1.2 
    @vue/babel-sugar-v-on:  1.1.2 
    @vue/cli-overlay:  4.2.2 
    @vue/cli-plugin-babel: ~4.2.0 => 4.2.2 
    @vue/cli-plugin-eslint: ~4.2.0 => 4.2.2 
    @vue/cli-plugin-router:  4.2.2 
    @vue/cli-plugin-typescript: ~4.2.0 => 4.2.2 
    @vue/cli-plugin-unit-jest: ~4.2.0 => 4.2.2 
    @vue/cli-plugin-vuex: ~4.2.0 => 4.2.2 
    @vue/cli-service: ~4.2.0 => 4.2.2 
    @vue/cli-shared-utils:  4.2.2 
    @vue/component-compiler-utils:  3.1.1 
    @vue/eslint-config-prettier: ^6.0.0 => 6.0.0 
    @vue/eslint-config-typescript: ^5.0.1 => 5.0.1 
    @vue/preload-webpack-plugin:  1.1.1 
    @vue/test-utils: 1.0.0-beta.31 => 1.0.0-beta.31 
    @vue/web-component-wrapper:  1.2.0 
    eslint-plugin-vue: ^6.1.2 => 6.2.1 
    jest-serializer-vue:  2.0.2 
    typescript: ~3.7.5 => 3.7.5 
    vue: ^2.6.11 => 2.6.11 
    vue-class-component: ^7.2.2 => 7.2.3 
    vue-eslint-parser:  7.0.0 
    vue-hot-reload-api:  2.3.4 
    vue-jest:  3.0.5 
    vue-loader:  15.9.0 
    vue-property-decorator: ^8.3.0 => 8.4.0 
    vue-style-loader:  4.1.2 
    vue-template-compiler: ^2.6.11 => 2.6.11 
    vue-template-es2015-compiler:  1.9.1 
    vuex: ^3.1.2 => 3.1.2 
  npmGlobalPackages:
    @vue/cli: 4.2.2

Reproduction link

https://github.com/i58/multipage

Steps to reproduce

  1. 运行 yarn build
  2. 注释掉vue.config.js中33、34行。 执行 yarn build

What is expected?

html页面可以正常引入vendors~xxx.js公共引用文件

What is actually happening?

注释掉preload插件

<html lang="en">
 <head>
  <meta charset="utf-8" />
  <meta http-equiv="X-UA-Compatible" content="IE=edge" />
  <meta name="viewport" content="width=device-width,initial-scale=1" />
  <link rel="icon" href="/favicon.ico" />
  <title>TEST</title>
  <link href="/static/css/index.4d7ae7bf.css" rel="stylesheet" />
 </head>
 <body>
  <noscript>
   <strong>We're sorry but TEST doesn't work properly without JavaScript enabled. Please enable it to continue.</strong>
  </noscript>
  <div id="app"></div>
  <script src="/static/js/index.eaef257c.js"></script>
 </body>
</html>

没有注释掉preload插件

<html lang="en">
 <head>
  <meta charset="utf-8" />
  <meta http-equiv="X-UA-Compatible" content="IE=edge" />
  <meta name="viewport" content="width=device-width,initial-scale=1" />
  <link rel="icon" href="/favicon.ico" />
  <title>TEST</title>
  <link href="/static/cssa/index.4d7ae7bf.css" rel="preload" as="style" />
  <link href="/static/js/index.4621eda1.js" rel="preload" as="script" />
  <link href="/static/js/vendors~help~index~order.60424b90.js" rel="preload" as="script" />
  <link href="/static/css/index.4d7ae7bf.css" rel="stylesheet" />
 </head>
 <body>
  <noscript>
   <strong>We're sorry but TEST doesn't work properly without JavaScript enabled. Please enable it to continue.</strong>
  </noscript>
  <div id="app"></div>
  <script src="/static/js/index.4621eda1.js"></script>
 </body>
</html>

所有build的文件都已经正常引用,但preload 模式下加载顺序有问题,不能正常执行代码

closed time in 10 hours

gezhigang1005

issue commentvuejs/vue-cli

multi-page配置删除preload插件无法注入vendors文件

Hello, thank you for taking time filling this issue!

However, we kindly ask you to use our Issue Helper when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatically closed by me (your robot friend!).

I hope to see your helper-created issue very soon!


你好,你的 issue 不符合我们所要求的格式,因此已被自动关闭。为了确保每个 issue 都提供必需的相关信息,请务必使用我们的 Issue 向导 来创建新 issue,谢谢!

gezhigang1005

comment created time in 10 hours

issue commentvuejs/vue-cli

webpack

Hello, thank you for taking time filling this issue!

However, we kindly ask you to use our Issue Helper when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatically closed by me (your robot friend!).

I hope to see your helper-created issue very soon!


你好,你的 issue 不符合我们所要求的格式,因此已被自动关闭。为了确保每个 issue 都提供必需的相关信息,请务必使用我们的 Issue 向导 来创建新 issue,谢谢!

yunzhongjing

comment created time in 20 hours

issue closedvuejs/vue

Garbled characters sometimes appear when using v-html such as: www.365station.com

www.365station.com content, generated by vue configuration

closed time in a day

969253189

issue commentvuejs/vue

Garbled characters sometimes appear when using v-html such as: www.365station.com

Hello, thank you for taking time filling this issue!

However, we kindly ask you to use our Issue Helper when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatically closed by me (your robot friend!).

I hope to see your helper-created issue very soon!

969253189

comment created time in a day

issue closedvuejs/vue

w使用 v-html 加载会出现乱码

<!-- IMPORTANT: Please use the following link to create a new issue:

https://new-issue.vuejs.org/

If your issue was not created using the app above, it will be closed immediately.

中文用户请注意: 请使用上面的链接来创建新的 issue。如果不是用上述工具创建的 issue 会被自动关闭。 -->

<!-- Love vuejs? Please consider supporting us via Patreon or OpenCollective: 👉 https://www.patreon.com/evanyou 👉 https://opencollective.com/vuejs/donate -->

closed time in a day

969253189

issue commentvuejs/vue

w使用 v-html 加载会出现乱码

Hello, thank you for taking time filling this issue!

However, we kindly ask you to use our Issue Helper when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatically closed by me (your robot friend!).

I hope to see your helper-created issue very soon!


你好,你的 issue 不符合我们所要求的格式,因此已被自动关闭。为了确保每个 issue 都提供必需的相关信息,请务必使用我们的 Issue 向导 来创建新 issue,谢谢!

969253189

comment created time in a day

issue closedvuejs/vue-router

Nested named route with parameter is redirected to the route name on refresh

Hi,

I am having this issue with the nested routes having parameter, when I refresh the page, the route loses the parameter and redirects to the route name instead. Please check the following code. Before refreshing the page http://localhost:8080/pos/tickets/1 and after refreshing http://localhost:8080/pos/ticketDetail <pre> { path: "/pos", name: "pos", component: Pos, meta: { requiresAuth: true }, children: [ ...... other child routes, { path: "tickets/:ticket_id", name: "ticketDetail", component: TicketDetail } ] } </pre> "vue": "^2.6.8", "vue-router": "^3.0.1"

Please advise?

closed time in 2 days

namoosalishah

issue commentvuejs/vue-router

Nested named route with parameter is redirected to the route name on refresh

Hello, thank you for taking time filling this issue!

However, we kindly ask you to use our Issue Helper when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatically closed by me (your robot friend!).

I hope to see your helper-created issue very soon!

namoosalishah

comment created time in 2 days

issue closedvuejs/vue-cli

sh: 1: vue-cli-service: Permission denied

I used Vue CLI to build vue project on GitHub actions like below:

name: ticket app CI

on: [push]

jobs:
  build:

    runs-on: ubuntu-latest

    strategy:
      matrix:
        node-version: [13.x]

    steps:
    - uses: actions/checkout@v2
    - name: Use Node.js ${{ matrix.node-version }}
      uses: actions/setup-node@v1
      with:
        node-version: ${{ matrix.node-version }}
    - run: npm install -g @vue/cli@latest
    - name: Build App
      working-directory: .
      run: |
        npm install
        npm run build

but the syntax runs with error and can not be complete.

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.11 (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.11: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
added 1053 packages from 457 contributors, updated 17 packages and audited 31510 packages in 19.722s


38 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

sh: 1: vue-cli-service: Permission denied

npm ERR! code ELIFECYCLE
> aiki-helpdesk@0.1.0 build /home/runner/work/Aiki-HelpDesk/Aiki-HelpDesk
npm ERR! errno 126
> vue-cli-service build
npm ERR! aiki-helpdesk@0.1.0 build: `vue-cli-service build`

npm ERR! Exit status 126
npm ERR! 
npm ERR! Failed at the aiki-helpdesk@0.1.0 build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/runner/.npm/_logs/2020-02-23T09_50_50_166Z-debug.log
##[error]Process completed with exit code 126.

closed time in 3 days

MohMehrnia

issue commentvuejs/vue-cli

sh: 1: vue-cli-service: Permission denied

Hello, thank you for taking time filling this issue!

However, we kindly ask you to use our Issue Helper when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatically closed by me (your robot friend!).

I hope to see your helper-created issue very soon!

MohMehrnia

comment created time in 3 days

issue closedvuejs/vue-cli

Issue helper is broken - api.github & CORS

CORS is blocking requests to the github API and I'm unable to submit new issues as a result of mandatory input fields.

- Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://api.github.com/repos/vuejs/vue-cli/releases?page=1&per_page=100. (Reason: CORS request did not succeed).
- TypeError: NetworkError when attempting to fetch resource.
- Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://api.github.com/search/issues?q=is:issue+repo:vuejs%2Fvue-cli+Update+@apollographql+dependencies. (Reason: CORS request did not succeed).

closed time in 5 days

TheIncorrigible1

issue commentvuejs/vue-cli

Issue helper is broken - api.github & CORS

Hello, thank you for taking time filling this issue!

However, we kindly ask you to use our Issue Helper when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatically closed by me (your robot friend!).

I hope to see your helper-created issue very soon!

TheIncorrigible1

comment created time in 5 days

issue closedvuejs/vue-router

History mode input URL and refresh will not enter the route guard or Axios global interception

History mode input URL and refresh will not enter the route guard or Axios global interception

What's the solution

closed time in 6 days

991567775

issue commentvuejs/vue-router

History mode input URL and refresh will not enter the route guard or Axios global interception

Hello, thank you for taking time filling this issue!

However, we kindly ask you to use our Issue Helper when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatically closed by me (your robot friend!).

I hope to see your helper-created issue very soon!

991567775

comment created time in 6 days

issue closedvuejs/vue-cli

js

IMPORTANT: Please use the following link to create a new issue:

https://new-issue.vuejs.org/?repo=vuejs/vue-cli

If your issue was not created using the app above, it will be closed immediately.

中文用户请注意: 请使用上面的链接来创建新的 issue。如果不是用上述工具创建的 issue 会被自动关闭。

closed time in 6 days

tomekhub

issue commentvuejs/vue-cli

js

Hello, thank you for taking time filling this issue!

However, we kindly ask you to use our Issue Helper when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatically closed by me (your robot friend!).

I hope to see your helper-created issue very soon!


你好,你的 issue 不符合我们所要求的格式,因此已被自动关闭。为了确保每个 issue 都提供必需的相关信息,请务必使用我们的 Issue 向导 来创建新 issue,谢谢!

tomekhub

comment created time in 6 days

issue closedvuejs/vue-cli

--inline-vue not working

Hi, i try to build a lib with vue inlined.

vue-cli-service build --target lib --inline-vue --name vueTrp

The Result locks so:

<meta charset="utf-8">
<title>vueTrp demo</title>
<script src="https://unpkg.com/vue"></script>
<script src="./vueTrp.umd.min.js"></script>


<div id="app">
  <demo></demo>
</div>

<script>
new Vue({
  components: {
    demo: vueTrp
  }
}).$mount('#app')
</script>

But I don't want to load Vue again. If i comment the line out <script src="https://unpkg.com/vue"></script> I get this error: demo:12 Uncaught ReferenceError: Vue is not defined

WHY?

closed time in 6 days

dertuerke

issue commentvuejs/vue-cli

--inline-vue not working

Hello, thank you for taking time filling this issue!

However, we kindly ask you to use our Issue Helper when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatically closed by me (your robot friend!).

I hope to see your helper-created issue very soon!

dertuerke

comment created time in 6 days

issue closedvuejs/vue-test-utils

How to test vuex action with change location?

In my vuex action, I change location window object. I have action with change location:

async setForm({ rootState, state, commit, dispatch }, formData) {
          ...

          switch (answ.result.type) {
            ...
            case 'redirect':
              console.log(answ.data.url);
              window.location = answ.data.url;
              console.log({ location: window.location.href });
              break;
            default:
              break;

My test function

    it('setForm - success, redirect', async done => {
      const formData = {
        status: 'success',
        result: {
          type: 'redirect',
          data: {
            url: 'https://www.google.ru/'
          }
        }
      };

      await store.dispatch(
        'deposit/setForm',
        formData,
        { root: true }
      );

      // delay for change location
      await new Promise(resolve => {
        setTimeout(() => { resolve(true); }, 1000);
      });

      expect(window.location.href).toBe('https://www.google.ru/');
    });

But, My location din't change.

    expect(received).toBe(expected) // Object.is equality

    Expected: "https://www.google.ru/"
    Received: "http://localhost/"

How to change location and tests it ?

closed time in 6 days

golubvladimir

issue commentvuejs/vue-test-utils

How to test vuex action with change location?

Hello, thank you for taking time filling this issue!

However, we kindly ask you to use our Issue Helper when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatically closed by me (your robot friend!).

I hope to see your helper-created issue very soon!

golubvladimir

comment created time in 6 days

issue closedvuejs/vuex

Vuex breaks with Vue 3.x

I've tried to run a Vue 3 application with Vuex, but when using it as a plugin I get the following error:

vuex.esm.js?2f62:7 Uncaught TypeError: Cannot read property 'split' of undefined
    at applyMixin (vuex.esm.js?2f62:7)
    at Object.install (vuex.esm.js?2f62:824)
    at Object.use (runtime-core.esm-bundler.js?5c40:1709)
    at eval (main.js?56d7:8)
    at Module../src/main.js (app.js:1246)
    at __webpack_require__ (app.js:786)
    at fn (app.js:151)
    at Object.1 (app.js:1356)
    at __webpack_require__ (app.js:786)
    at checkDeferredModules (app.js:46)

Which leads to the point where it tries to determine the Vue version from the global Vue instance, which is non-existent.

var version = Number(Vue.version.split('.')[0]);

Any suggestions on how to add Vuex to Vue 3 projects? There is an exported variable in Vue 3 called version.

closed time in 7 days

blacksonic

issue commentvuejs/vuex

Vuex breaks with Vue 3.x

Hello, thank you for taking time filling this issue!

However, we kindly ask you to use our Issue Helper when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatically closed by me (your robot friend!).

I hope to see your helper-created issue very soon!

blacksonic

comment created time in 7 days

issue closedvuejs/vue-cli

how do used in github actions

hi, how do used vue cli in github actions?

closed time in 8 days

MohMehrnia

issue commentvuejs/vue-cli

how do used in github actions

Hello, thank you for taking time filling this issue!

However, we kindly ask you to use our Issue Helper when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatically closed by me (your robot friend!).

I hope to see your helper-created issue very soon!

MohMehrnia

comment created time in 8 days

issue closedvuejs/vue

beforeDestroy

beforeDestroy event does not work like the $ destroy event of the angular. I've used keepalive and it still doesn't work.

How do I update a page with F5 and receive the event before Destroy.

Angular $scope.$on('$destroy', function () { Service.terminar(); }); 1 2

closed time in 8 days

talktelecom

issue commentvuejs/vue

beforeDestroy

Hello, thank you for taking time filling this issue!

However, we kindly ask you to use our Issue Helper when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatically closed by me (your robot friend!).

I hope to see your helper-created issue very soon!

talktelecom

comment created time in 8 days

issue closedvuejs/vue

Wanna see my private photos?💋💋💋

Hello!😻😻😻 Wanna see my private photos?💋💋💋 Go to this site and find me here. ❤️❤️❤️ My nick is pussycat18 👇👇👇

https://tinyurl.com/wyb476h

closed time in 9 days

scdsfvd

issue commentvuejs/vue

Wanna see my private photos?💋💋💋

Hello, thank you for taking time filling this issue!

However, we kindly ask you to use our Issue Helper when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatically closed by me (your robot friend!).

I hope to see your helper-created issue very soon!

scdsfvd

comment created time in 9 days

issue closedvuejs/vue

Wanna see my private photos?💋💋💋

Hello!😻😻😻 Wanna see my private photos?💋💋💋 Go to this site and find me here. ❤️❤️❤️ My nick is pussycat18 👇👇👇

https://tinyurl.com/rupocj5

closed time in 9 days

heken375

issue commentvuejs/vue

Wanna see my private photos?💋💋💋

Hello, thank you for taking time filling this issue!

However, we kindly ask you to use our Issue Helper when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatically closed by me (your robot friend!).

I hope to see your helper-created issue very soon!

heken375

comment created time in 9 days

issue closedvuejs/vue

Wanna see my hot pics?💋💋💋

Hi!😻😻😻 Wanna see my hot pics?💋💋💋 Go to this site and find me here. ❤️❤️❤️ My nick is sexygirl662 👇👇👇

https://tinyurl.com/tza85ua

closed time in 9 days

helen773

issue commentvuejs/vue

Wanna see my hot pics?💋💋💋

Hello, thank you for taking time filling this issue!

However, we kindly ask you to use our Issue Helper when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatically closed by me (your robot friend!).

I hope to see your helper-created issue very soon!

helen773

comment created time in 9 days

issue commentvuejs/vue

Wanna see my hot pics?💋💋💋

Hello, thank you for taking time filling this issue!

However, we kindly ask you to use our Issue Helper when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatically closed by me (your robot friend!).

I hope to see your helper-created issue very soon!

helen119

comment created time in 9 days

issue closedvuejs/vue

Wanna see my hot pics?💋💋💋

Hi!😻😻😻 Wanna see my hot pics?💋💋💋 Go to this site and find me here. ❤️❤️❤️ My nick is sexygirl662 👇👇👇

https://tinyurl.com/ulpu2gz

closed time in 9 days

helen119

issue closedvuejs/vue

WU AND MG TRANSFERS FOR 10-15% OF THE AMOUNT!!! 💰💰💰

WU AND MG TRANSFERS FOR 10-15% OF THE AMOUNT!!!

FOR EXAMPLE:

WORLD WIDE WESTERN UNION & MONEYGRAM PRICES:

You pay: [ 299 $ BitCoin / PerfectMoney ] You receive: [ $2000 WU or MG ] You pay: [ 390 $ BitCoin / PerfectMoney ] You receive: [ $3000 WU or MG ] You pay: [ 480 $ BitCoin / PerfectMoney ] You receive: [ $4000 WU or MG ] You pay: [ 570 $ BitCoin / PerfectMoney ] You receive: [ $5000 WU or MG ] You pay: [ 660 $ BitCoin / PerfectMoney ] You receive: [ $6000 WU or MG ] You pay: [ 750 $ BitCoin / PerfectMoney ] You receive: [ $7000 WU or MG ] You pay: [ 800 $ BitCoin / PerfectMoney ] You receive: [ $8000 WU or MG ] You pay: [ 850 $ BitCoin / PerfectMoney ] You receive: [$9000 WU or MG ] (You will get 2 MTCN's. 4500$ and 4500$) You pay: [ 899 $ BitCoin / PerfectMoney ] You receive: [$9990 WU or MG ] (You will get 2 MTCN's. 4995$ and 4995$)

👇👇👇

https://tinyurl.com/sr7r3e4

closed time in 9 days

akdnfbf

issue commentvuejs/vue

WU AND MG TRANSFERS FOR 10-15% OF THE AMOUNT!!! 💰💰💰

Hello, thank you for taking time filling this issue!

However, we kindly ask you to use our Issue Helper when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatically closed by me (your robot friend!).

I hope to see your helper-created issue very soon!

akdnfbf

comment created time in 9 days

issue closedvuejs/vue

Wanna see my hot pics?💋💋💋

Hi!😻😻😻 Wanna see my hot pics?💋💋💋 Go to this site and find me here. ❤️❤️❤️ My nick is sexygirl662 👇👇👇

https://tinyurl.com/sbmadwq

closed time in 9 days

akdnfbf

issue commentvuejs/vue

Wanna see my hot pics?💋💋💋

Hello, thank you for taking time filling this issue!

However, we kindly ask you to use our Issue Helper when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatically closed by me (your robot friend!).

I hope to see your helper-created issue very soon!

akdnfbf

comment created time in 9 days

issue closedvuejs/rollup-plugin-vue

Feature suggestion: mapping '@' import path to the source folder?

Vue CLI maps @/... paths to the src folder, at least by:

In in the scaffolding that vue-cli cranks out for you, part of the base webpack config sets up an alias for .vue files:

Source

Using Vue with Rollup (and no Vue CLI), it took me a while to realise the mapping wasn't part of Vue. Would it make sense to have rollup-plugin-vue add this feature in, if technically possible?

I'm currently doing it with:

// rollup.config.js
import alias from '@rollup/plugin-alias';

...
  // For '@/...' to work like it does for Vue CLI -configured projects.
  alias({
    entries: {
      ['@']: __dirname + '/src'    // path.resolve( __dirname, 'src' )    // <-- no idea why 'path' is not found. tbd.
    }

This is the only reason I have for plugin-alias. Question likely is: is use of @/ seen as a Vue thing, or is it something that's simply a build configuration pattern?

closed time in 10 days

akauppi

issue commentvuejs/rollup-plugin-vue

Feature suggestion: mapping '@' import path to the source folder?

Hello, thank you for taking time filling this issue!

However, we kindly ask you to use our Issue Helper when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatically closed by me (your robot friend!).

I hope to see your helper-created issue very soon!

akauppi

comment created time in 10 days

pull request commentvuejs/eslint-plugin-vue

New: attributes-order adding alphabetical ordering within groupings

Hey @erindepew, thank you for your time and effort spent on this PR, contributions like yours help make Vue better for everyone. Cheers! 💚

erindepew

comment created time in 10 days

issue closedvuejs/vue-cli

one suggestion

In vue project created by vue-cli, we can't jump to the child components by click the child components tag. However, it's enabled in react project created by create-react-app.

closed time in 11 days

HuYong66

issue commentvuejs/vue-cli

one suggestion

Hello, thank you for taking time filling this issue!

However, we kindly ask you to use our Issue Helper when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatically closed by me (your robot friend!).

I hope to see your helper-created issue very soon!

HuYong66

comment created time in 11 days

issue closedvuejs/vue-loader

Data-Attributes on Scoped Nested SCSS not applied to correct elements

<!-- IMPORTANT: Please use the following link to create a new issue:

https://new-issue.vuejs.org/?repo=vuejs/vue-loader

If your issue was not created using the app above, it will be closed immediately. -->

Let's say I have this SCSS in a component marked to have Scoped css with a .scss file referenced through the src attribute.

<style scoped lang="scss" src="./styles.scss"></style>

// Styles.scss
#custom-menu {
    z-index          : 1000;

    ol {
        padding     : 0;

        li {
            margin     : 0;
    }

}

This gets incorrectly rendered as

#custom-menu[data-v-460e287f] {
    z-index          : 1000;
}

#custom-menu ol[data-v-460e287f] {
    padding     : 0;
}

#custom-menu ol li[data-v-460e287f] {
    margin     : 0;
}

And here is the HTML

<div data-v-460e287f="" id="custom-menu">
   <ol>
        <li class="context-menu-item">Item</li>
   </ol>
</div>

Notice how the data attribute is added to the #cusom-menu element in the HTML, but in the CSS it's added to the last selector in the nested SCSS. So the styles do not render correctly with the HTML as generated.

Solution: Data attribute should be added to the root element of a nested SCSS tag, not the individual elements nested in it.

closed time in 13 days

IAMtheIAM

issue commentvuejs/vue-loader

Data-Attributes on Scoped Nested SCSS not applied to correct elements

Hello, thank you for taking time filling this issue!

However, we kindly ask you to use our Issue Helper when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatically closed by me (your robot friend!).

I hope to see your helper-created issue very soon!

IAMtheIAM

comment created time in 13 days

issue closedvuejs/vue-cli

SSL Configuration Issue

SSL Configuration Issue

I have created the project used by vue-cli. And called an API method, got the following error. Network error from origin 'http://localhost:8080' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: It does not have HTTP ok status

I have created the vue.config.js file and configured ssl certificate path in vue.config.js.
vue.config.js const fs = require('fs'); module.exports = { devServer: { https: { key: fs.readFileSync('./my certificate file name.key'), cert: fs.readFileSync('./my certificate file name.crt'), }, }, };

I can able to compile the project, but in the browser it shows “https is not working” error. (https://mydomain.com:8080)

ref1

ref2

ref3

So I have tried to configure the host address in vue.config.js file. devServer: { host: “xx.xx.xx.xx”,//my domain.com https: { key: fs.readFileSync('./my certificate file name.key'), cert: fs.readFileSync('./my certificate file name.crt'),
} }

After I compile, I got this error listen EADDRNOTAVAIL: address not available xx.xx.xx.xx:5000

ref4

closed time in 13 days

prakash50166

issue commentvuejs/vue-cli

SSL Configuration Issue

Hello, thank you for taking time filling this issue!

However, we kindly ask you to use our Issue Helper when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatically closed by me (your robot friend!).

I hope to see your helper-created issue very soon!

prakash50166

comment created time in 13 days

issue closedvuejs/vue-router

Vue router version 3.1.5 hash mode redirect to 1 page before

solution : rollback to version 3.1.3 solve the issue ...

closed time in 13 days

drmmyx

issue commentvuejs/vue-router

Vue router version 3.1.5 hash mode redirect to 1 page before

Hello, thank you for taking time filling this issue!

However, we kindly ask you to use our Issue Helper when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatically closed by me (your robot friend!).

I hope to see your helper-created issue very soon!

drmmyx

comment created time in 13 days

issue closedvuejs/vue

Syntax suggestion when passing props to components

Hello, I'd like to suggest the following syntax that you may add to future releases.

<my-component ::params @@myMethod />

Could be equivalent to

<my-component :params="params" @myMethod="myMethod" />

That would make code much cleaner when we have to pass multiple props to a child component and those props have the same name as the variables in the parent component. The same thing can be said about events.

I hope you take this into consideration and that my suggestion will help you improve VUE.

closed time in 14 days

AndreSouzaAbreu

issue commentvuejs/vue

Syntax suggestion when passing props to components

Hello, thank you for taking time filling this issue!

However, we kindly ask you to use our Issue Helper when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatically closed by me (your robot friend!).

I hope to see your helper-created issue very soon!

AndreSouzaAbreu

comment created time in 14 days

issue closedvuejs/vue-test-utils

The methods on the website is empty!

<!-- IMPORTANT: Please use the following link to create a new issue:

https://new-issue.vuejs.org/?repo=vuejs/vue-test-utils

If your issue was not created using the app above, it will be closed immediately. --> https://vue-test-utils.vuejs.org/api/wrapper-array/#methods Hello, while trying to find out how to call a method, I see that the method section is empty, is that intentional or a mistake? Thank you

closed time in 14 days

TimSun-Code

issue commentvuejs/vue-test-utils

The methods on the website is empty!

Hello, thank you for taking time filling this issue!

However, we kindly ask you to use our Issue Helper when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatically closed by me (your robot friend!).

I hope to see your helper-created issue very soon!

TimSun-Code

comment created time in 14 days

issue closedvuejs/vue-cli

vue create npm ERR! 404 Not Found - GET https://registry.npmjs.org/error-ex

Below error comes when creating new project `Vue CLI v4.1.2 ✨ Creating project in C:\Users\dany\Desktop\hello2. 🗃 Initializing git repository... ⚙ Installing CLI plugins. This might take a while...

npm ERR! code E404 npm ERR! 404 Not Found - GET https://registry.npmjs.org/error-ex npm ERR! 404 npm ERR! 404 'error-ex@^1.3.1' is not in the npm registry. npm ERR! 404 You should bug the author to publish it (or use the name yourself!) npm ERR! 404 It was specified as a dependency of 'parse-json' npm ERR! 404 npm ERR! 404 Note that you can also install from a npm ERR! 404 tarball, folder, http url, or git url.

npm ERR! A complete log of this run can be found in: npm ERR! C:\Users\dany\AppData\Roaming\npm-cache_logs\2020-02-12T12_57_45_506Z-debug.log ERROR command failed: npm install --loglevel error --registry=https://registry.npmjs.org/ `

closed time in 14 days

danywalls

issue commentvuejs/vue-cli

vue create npm ERR! 404 Not Found - GET https://registry.npmjs.org/error-ex

Hello, thank you for taking time filling this issue!

However, we kindly ask you to use our Issue Helper when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatically closed by me (your robot friend!).

I hope to see your helper-created issue very soon!

danywalls

comment created time in 14 days

issue closedvuejs/vue-cli

Unable to install @vue/cli or install dependecies

Unable to install vue cli globally or install my project dependencies.

Installation fails with 404 Not Found - GET https://registry.npmjs.org/error-ex.

0 info it worked if it ends with ok 1 verbose cli [ 1 verbose cli '/usr/local/Cellar/node@12/12.15.0/bin/node', 1 verbose cli '/usr/local/bin/npm', 1 verbose cli 'install', 1 verbose cli '@vue/cli' 1 verbose cli ] 2 info using npm@6.13.7 3 info using node@v12.15.0 4 verbose npm-session fa4cf840264f3567 5 silly install loadCurrentTree 6 silly install readLocalPackageData 7 http fetch GET 304 https://registry.npmjs.org/@vue%2fcli 756ms (from cache) 8 silly pacote tag manifest for @vue/cli@latest fetched in 768ms 9 timing stage:loadCurrentTree Completed in 805ms 10 silly install loadIdealTree 11 silly install cloneCurrentTreeToIdealTree 12 timing stage:loadIdealTree:cloneCurrentTree Completed in 0ms 13 silly install loadShrinkwrap 14 timing stage:loadIdealTree:loadShrinkwrap Completed in 0ms 15 silly install loadAllDepsIntoIdealTree 16 silly resolveWithNewModule @vue/cli@4.2.2 checking installable status 17 http fetch GET 200 https://registry.npmjs.org/boxen 31ms (from cache) 18 http fetch GET 200 https://registry.npmjs.org/didyoumean 26ms (from cache) 19 silly pacote range manifest for boxen@^4.1.0 fetched in 34ms 20 silly resolveWithNewModule boxen@4.2.0 checking installable status 21 silly pacote range manifest for didyoumean@^1.2.1 fetched in 30ms 22 silly resolveWithNewModule didyoumean@1.2.1 checking installable status 23 http fetch GET 304 https://registry.npmjs.org/@vue%2fcli-shared-utils 214ms (from cache) 24 silly pacote range manifest for @vue/cli-shared-utils@^4.2.2 fetched in 218ms 25 silly resolveWithNewModule @vue/cli-shared-utils@4.2.2 checking installable status 26 http fetch GET 304 https://registry.npmjs.org/envinfo 174ms (from cache) 27 silly pacote range manifest for envinfo@^7.5.0 fetched in 178ms 28 silly resolveWithNewModule envinfo@7.5.0 checking installable status 29 http fetch GET 304 https://registry.npmjs.org/cmd-shim 572ms (from cache) 30 http fetch GET 304 https://registry.npmjs.org/ejs 537ms (from cache) 31 http fetch GET 304 https://registry.npmjs.org/download-git-repo 541ms (from cache) 32 http fetch GET 304 https://registry.npmjs.org/debug 574ms (from cache) 33 http fetch GET 304 https://registry.npmjs.org/deepmerge 573ms (from cache) 34 http fetch GET 304 https://registry.npmjs.org/@vue%2fcli-ui-addon-widgets 581ms (from cache) 35 silly pacote range manifest for cmd-shim@^3.0.3 fetched in 580ms 36 silly resolveWithNewModule cmd-shim@3.0.3 checking installable status 37 silly pacote range manifest for ejs@^2.7.1 fetched in 546ms 38 silly resolveWithNewModule ejs@2.7.4 checking installable status 39 silly pacote range manifest for download-git-repo@^1.0.2 fetched in 550ms 40 silly resolveWithNewModule download-git-repo@1.1.0 checking installable status 41 http fetch GET 304 https://registry.npmjs.org/@vue%2fcli-ui-addon-webpack 587ms (from cache) 42 silly pacote range manifest for debug@^4.1.0 fetched in 585ms 43 silly resolveWithNewModule debug@4.1.1 checking installable status 44 silly pacote range manifest for deepmerge@^4.2.2 fetched in 584ms 45 silly resolveWithNewModule deepmerge@4.2.2 checking installable status 46 silly pacote range manifest for @vue/cli-ui-addon-widgets@^4.2.2 fetched in 592ms 47 silly resolveWithNewModule @vue/cli-ui-addon-widgets@4.2.2 checking installable status 48 silly pacote range manifest for @vue/cli-ui-addon-webpack@^4.2.2 fetched in 599ms 49 silly resolveWithNewModule @vue/cli-ui-addon-webpack@4.2.2 checking installable status 50 http fetch GET 304 https://registry.npmjs.org/fs-extra 215ms (from cache) 51 silly pacote range manifest for fs-extra@^7.0.1 fetched in 216ms 52 silly resolveWithNewModule fs-extra@7.0.1 checking installable status 53 http fetch GET 304 https://registry.npmjs.org/@vue%2fcli-ui 613ms (from cache) 54 silly pacote range manifest for @vue/cli-ui@^4.2.2 fetched in 617ms 55 silly resolveWithNewModule @vue/cli-ui@4.2.2 checking installable status 56 http fetch GET 304 https://registry.npmjs.org/commander 772ms (from cache) 57 silly pacote range manifest for commander@^2.20.0 fetched in 773ms 58 silly resolveWithNewModule commander@2.20.3 checking installable status 59 http fetch GET 304 https://registry.npmjs.org/js-yaml 217ms (from cache) 60 http fetch GET 304 https://registry.npmjs.org/globby 228ms (from cache) 61 http fetch GET 304 https://registry.npmjs.org/javascript-stringify 222ms (from cache) 62 http fetch GET 304 https://registry.npmjs.org/jscodeshift 215ms (from cache) 63 http fetch GET 304 https://registry.npmjs.org/isbinaryfile 226ms (from cache) 64 http fetch GET 304 https://registry.npmjs.org/import-global 233ms (from cache) 65 silly pacote range manifest for js-yaml@^3.13.1 fetched in 224ms 66 silly resolveWithNewModule js-yaml@3.13.1 checking installable status 67 http fetch GET 304 https://registry.npmjs.org/lodash.clonedeep 209ms (from cache) 68 silly pacote range manifest for globby@^9.2.0 fetched in 239ms 69 silly resolveWithNewModule globby@9.2.0 checking installable status 70 silly pacote range manifest for javascript-stringify@^1.6.0 fetched in 231ms 71 silly resolveWithNewModule javascript-stringify@1.6.0 checking installable status 72 silly pacote range manifest for jscodeshift@^0.7.0 fetched in 224ms 73 silly resolveWithNewModule jscodeshift@0.7.0 checking installable status 74 silly pacote range manifest for isbinaryfile@^4.0.0 fetched in 237ms 75 silly resolveWithNewModule isbinaryfile@4.0.4 checking installable status 76 silly pacote range manifest for import-global@^0.1.0 fetched in 243ms 77 silly resolveWithNewModule import-global@0.1.0 checking installable status 78 http fetch GET 304 https://registry.npmjs.org/lru-cache 213ms (from cache) 79 http fetch GET 304 https://registry.npmjs.org/inquirer 243ms (from cache) 80 silly pacote range manifest for lodash.clonedeep@^4.5.0 fetched in 221ms 81 silly resolveWithNewModule lodash.clonedeep@4.5.0 checking installable status 82 silly pacote range manifest for lru-cache@^5.1.1 fetched in 228ms 83 silly resolveWithNewModule lru-cache@5.1.1 checking installable status 84 silly pacote range manifest for inquirer@^6.3.1 fetched in 257ms 85 silly resolveWithNewModule inquirer@6.5.2 checking installable status 86 http fetch GET 200 https://registry.npmjs.org/shortid 20ms (from cache) 87 silly pacote range manifest for shortid@^2.2.15 fetched in 22ms 88 silly resolveWithNewModule shortid@2.2.15 checking installable status 89 http fetch GET 304 https://registry.npmjs.org/minimist 172ms (from cache) 90 silly pacote range manifest for minimist@^1.2.0 fetched in 173ms 91 silly resolveWithNewModule minimist@1.2.0 checking installable status 92 http fetch GET 304 https://registry.npmjs.org/slash 200ms (from cache) 93 http fetch GET 304 https://registry.npmjs.org/recast 206ms (from cache) 94 silly pacote range manifest for slash@^3.0.0 fetched in 205ms 95 silly resolveWithNewModule slash@3.0.0 checking installable status 96 silly pacote range manifest for recast@^0.18.1 fetched in 212ms 97 silly resolveWithNewModule recast@0.18.5 checking installable status 98 http fetch GET 304 https://registry.npmjs.org/vue-jscodeshift-adapter 205ms (from cache) 99 http fetch GET 304 https://registry.npmjs.org/yaml-front-matter 201ms (from cache) 100 silly pacote range manifest for vue-jscodeshift-adapter@^2.0.2 fetched in 208ms 101 silly resolveWithNewModule vue-jscodeshift-adapter@2.0.3 checking installable status 102 silly pacote range manifest for yaml-front-matter@^3.4.1 fetched in 204ms 103 silly resolveWithNewModule yaml-front-matter@3.4.1 checking installable status 104 http fetch GET 304 https://registry.npmjs.org/validate-npm-package-name 210ms (from cache) 105 http fetch GET 304 https://registry.npmjs.org/resolve 213ms (from cache) 106 silly pacote range manifest for validate-npm-package-name@^3.0.0 fetched in 212ms 107 silly resolveWithNewModule validate-npm-package-name@3.0.0 checking installable status 108 silly pacote range manifest for resolve@^1.15.0 fetched in 216ms 109 silly resolveWithNewModule resolve@1.15.1 checking installable status 110 http fetch GET 304 https://registry.npmjs.org/execa 201ms (from cache) 111 silly pacote range manifest for execa@^1.0.0 fetched in 206ms 112 silly resolveWithNewModule execa@1.0.0 checking installable status 113 http fetch GET 304 https://registry.npmjs.org/node-ipc 211ms (from cache) 114 http fetch GET 304 https://registry.npmjs.org/launch-editor 212ms (from cache) 115 http fetch GET 304 https://registry.npmjs.org/ora 211ms (from cache) 116 http fetch GET 304 https://registry.npmjs.org/request-promise-native 211ms (from cache) 117 http fetch GET 304 https://registry.npmjs.org/chalk 214ms (from cache) 118 http fetch GET 304 https://registry.npmjs.org/read-pkg 215ms (from cache) 119 http fetch GET 304 https://registry.npmjs.org/request 216ms (from cache) 120 silly pacote range manifest for node-ipc@^9.1.1 fetched in 219ms 121 silly resolveWithNewModule node-ipc@9.1.1 checking installable status 122 silly pacote range manifest for launch-editor@^2.2.1 fetched in 220ms 123 silly resolveWithNewModule launch-editor@2.2.1 checking installable status 124 silly pacote range manifest for ora@^3.4.0 fetched in 220ms 125 silly resolveWithNewModule ora@3.4.0 checking installable status 126 silly pacote range manifest for chalk@^2.4.2 fetched in 222ms 127 silly resolveWithNewModule chalk@2.4.2 checking installable status 128 silly pacote range manifest for request-promise-native@^1.0.8 fetched in 221ms 129 silly resolveWithNewModule request-promise-native@1.0.8 checking installable status 130 silly pacote range manifest for read-pkg@^5.1.1 fetched in 223ms 131 silly resolveWithNewModule read-pkg@5.2.0 checking installable status 132 http fetch GET 304 https://registry.npmjs.org/open 225ms (from cache) 133 http fetch GET 304 https://registry.npmjs.org/@hapi%2fjoi 227ms (from cache) 134 silly pacote range manifest for request@^2.87.0 fetched in 226ms 135 warn deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142 136 silly resolveWithNewModule request@2.88.2 checking installable status 137 silly pacote range manifest for open@^6.3.0 fetched in 229ms 138 silly resolveWithNewModule open@6.4.0 checking installable status 139 silly pacote range manifest for @hapi/joi@^15.0.1 fetched in 231ms 140 silly resolveWithNewModule @hapi/joi@15.1.1 checking installable status 141 http fetch GET 304 https://registry.npmjs.org/semver 176ms (from cache) 142 silly pacote range manifest for semver@^6.1.0 fetched in 178ms 143 silly resolveWithNewModule semver@6.3.0 checking installable status 144 http fetch GET 304 https://registry.npmjs.org/strip-ansi 184ms (from cache) 145 silly pacote range manifest for strip-ansi@^6.0.0 fetched in 184ms 146 silly resolveWithNewModule strip-ansi@6.0.0 checking installable status 147 http fetch GET 304 https://registry.npmjs.org/@hapi%2fhoek 191ms (from cache) 148 http fetch GET 304 https://registry.npmjs.org/@hapi%2ftopo 192ms (from cache) 149 silly pacote range manifest for @hapi/hoek@8.x.x fetched in 193ms 150 silly resolveWithNewModule @hapi/hoek@8.5.1 checking installable status 151 silly pacote range manifest for @hapi/topo@3.x.x fetched in 194ms 152 silly resolveWithNewModule @hapi/topo@3.1.6 checking installable status 153 http fetch GET 304 https://registry.npmjs.org/@hapi%2faddress 196ms (from cache) 154 http fetch GET 304 https://registry.npmjs.org/@hapi%2fbourne 197ms (from cache) 155 silly pacote range manifest for @hapi/address@2.x.x fetched in 197ms 156 silly resolveWithNewModule @hapi/address@2.1.4 checking installable status 157 silly pacote range manifest for @hapi/bourne@1.x.x fetched in 198ms 158 silly resolveWithNewModule @hapi/bourne@1.3.2 checking installable status 159 http fetch GET 304 https://registry.npmjs.org/supports-color 198ms (from cache) 160 http fetch GET 304 https://registry.npmjs.org/ansi-styles 200ms (from cache) 161 silly pacote range manifest for supports-color@^5.3.0 fetched in 200ms 162 silly resolveWithNewModule supports-color@5.5.0 checking installable status 163 silly pacote range manifest for ansi-styles@^3.2.1 fetched in 201ms 164 silly resolveWithNewModule ansi-styles@3.2.1 checking installable status 165 http fetch GET 304 https://registry.npmjs.org/escape-string-regexp 213ms (from cache) 166 silly pacote range manifest for escape-string-regexp@^1.0.5 fetched in 213ms 167 silly resolveWithNewModule escape-string-regexp@1.0.5 checking installable status 168 http fetch GET 304 https://registry.npmjs.org/color-convert 173ms (from cache) 169 silly pacote range manifest for color-convert@^1.9.0 fetched in 174ms 170 silly resolveWithNewModule color-convert@1.9.3 checking installable status 171 http fetch GET 304 https://registry.npmjs.org/color-name 179ms (from cache) 172 silly pacote version manifest for color-name@1.1.3 fetched in 180ms 173 silly resolveWithNewModule color-name@1.1.3 checking installable status 174 http fetch GET 304 https://registry.npmjs.org/has-flag 178ms (from cache) 175 silly pacote range manifest for has-flag@^3.0.0 fetched in 179ms 176 silly resolveWithNewModule has-flag@3.0.0 checking installable status 177 http fetch GET 200 https://registry.npmjs.org/get-stream 10ms (from cache) 178 silly pacote range manifest for get-stream@^4.0.0 fetched in 10ms 179 silly resolveWithNewModule get-stream@4.1.0 checking installable status 180 http fetch GET 304 https://registry.npmjs.org/is-stream 205ms (from cache) 181 http fetch GET 304 https://registry.npmjs.org/strip-eof 205ms (from cache) 182 silly pacote range manifest for is-stream@^1.1.0 fetched in 208ms 183 silly resolveWithNewModule is-stream@1.1.0 checking installable status 184 silly pacote range manifest for strip-eof@^1.0.0 fetched in 207ms 185 silly resolveWithNewModule strip-eof@1.0.0 checking installable status 186 http fetch GET 304 https://registry.npmjs.org/npm-run-path 211ms (from cache) 187 http fetch GET 304 https://registry.npmjs.org/signal-exit 211ms (from cache) 188 silly pacote range manifest for npm-run-path@^2.0.0 fetched in 213ms 189 silly resolveWithNewModule npm-run-path@2.0.2 checking installable status 190 http fetch GET 304 https://registry.npmjs.org/p-finally 212ms (from cache) 191 silly pacote range manifest for signal-exit@^3.0.0 fetched in 213ms 192 silly resolveWithNewModule signal-exit@3.0.2 checking installable status 193 silly pacote range manifest for p-finally@^1.0.0 fetched in 214ms 194 silly resolveWithNewModule p-finally@1.0.0 checking installable status 195 http fetch GET 304 https://registry.npmjs.org/cross-spawn 216ms (from cache) 196 silly pacote range manifest for cross-spawn@^6.0.0 fetched in 219ms 197 silly resolveWithNewModule cross-spawn@6.0.5 checking installable status 198 silly pacote range manifest for semver@^5.5.0 fetched in 4ms 199 silly resolveWithNewModule semver@5.7.1 checking installable status 200 http fetch GET 304 https://registry.npmjs.org/shebang-command 195ms (from cache) 201 http fetch GET 304 https://registry.npmjs.org/path-key 195ms (from cache) 202 http fetch GET 304 https://registry.npmjs.org/nice-try 196ms (from cache) 203 http fetch GET 304 https://registry.npmjs.org/which 197ms (from cache) 204 silly pacote range manifest for shebang-command@^1.2.0 fetched in 197ms 205 silly resolveWithNewModule shebang-command@1.2.0 checking installable status 206 silly pacote range manifest for path-key@^2.0.1 fetched in 198ms 207 silly resolveWithNewModule path-key@2.0.1 checking installable status 208 silly pacote range manifest for nice-try@^1.0.4 fetched in 199ms 209 silly resolveWithNewModule nice-try@1.0.5 checking installable status 210 silly pacote range manifest for which@^1.2.9 fetched in 199ms 211 silly resolveWithNewModule which@1.3.1 checking installable status 212 http fetch GET 304 https://registry.npmjs.org/shebang-regex 175ms (from cache) 213 silly pacote range manifest for shebang-regex@^1.0.0 fetched in 176ms 214 silly resolveWithNewModule shebang-regex@1.0.0 checking installable status 215 http fetch GET 304 https://registry.npmjs.org/isexe 188ms (from cache) 216 silly pacote range manifest for isexe@^2.0.0 fetched in 188ms 217 silly resolveWithNewModule isexe@2.0.0 checking installable status 218 http fetch GET 304 https://registry.npmjs.org/pump 167ms (from cache) 219 silly pacote range manifest for pump@^3.0.0 fetched in 168ms 220 silly resolveWithNewModule pump@3.0.0 checking installable status 221 http fetch GET 304 https://registry.npmjs.org/once 171ms (from cache) 222 silly pacote range manifest for once@^1.3.1 fetched in 172ms 223 silly resolveWithNewModule once@1.4.0 checking installable status 224 http fetch GET 304 https://registry.npmjs.org/end-of-stream 176ms (from cache) 225 silly pacote range manifest for end-of-stream@^1.1.0 fetched in 176ms 226 silly resolveWithNewModule end-of-stream@1.4.4 checking installable status 227 http fetch GET 304 https://registry.npmjs.org/wrappy 178ms (from cache) 228 silly pacote range manifest for wrappy@1 fetched in 179ms 229 silly resolveWithNewModule wrappy@1.0.2 checking installable status 230 http fetch GET 304 https://registry.npmjs.org/shell-quote 215ms (from cache) 231 silly pacote range manifest for shell-quote@^1.6.1 fetched in 216ms 232 silly resolveWithNewModule shell-quote@1.7.2 checking installable status 233 http fetch GET 200 https://registry.npmjs.org/yallist 2ms (from cache) 234 silly pacote range manifest for yallist@^3.0.2 fetched in 3ms 235 silly resolveWithNewModule yallist@3.1.1 checking installable status 236 http fetch GET 304 https://registry.npmjs.org/js-message 253ms (from cache) 237 http fetch GET 304 https://registry.npmjs.org/js-queue 253ms (from cache) 238 http fetch GET 304 https://registry.npmjs.org/event-pubsub 254ms (from cache) 239 silly pacote version manifest for js-message@1.0.5 fetched in 254ms 240 silly resolveWithNewModule js-message@1.0.5 checking installable status 241 silly pacote version manifest for js-queue@2.0.0 fetched in 255ms 242 silly resolveWithNewModule js-queue@2.0.0 checking installable status 243 silly pacote version manifest for event-pubsub@4.3.0 fetched in 255ms 244 silly resolveWithNewModule event-pubsub@4.3.0 checking installable status 245 http fetch GET 304 https://registry.npmjs.org/easy-stack 204ms (from cache) 246 silly pacote range manifest for easy-stack@^1.0.0 fetched in 204ms 247 silly resolveWithNewModule easy-stack@1.0.0 checking installable status 248 http fetch GET 304 https://registry.npmjs.org/is-wsl 204ms (from cache) 249 silly pacote range manifest for is-wsl@^1.1.0 fetched in 205ms 250 silly resolveWithNewModule is-wsl@1.1.0 checking installable status 251 silly pacote range manifest for strip-ansi@^5.2.0 fetched in 2ms 252 silly resolveWithNewModule strip-ansi@5.2.0 checking installable status 253 http fetch GET 304 https://registry.npmjs.org/cli-spinners 189ms (from cache) 254 http fetch GET 304 https://registry.npmjs.org/cli-cursor 190ms (from cache) 255 silly pacote range manifest for cli-spinners@^2.0.0 fetched in 191ms 256 silly resolveWithNewModule cli-spinners@2.2.0 checking installable status 257 silly pacote range manifest for cli-cursor@^2.1.0 fetched in 192ms 258 silly resolveWithNewModule cli-cursor@2.1.0 checking installable status 259 http fetch GET 304 https://registry.npmjs.org/wcwidth 193ms (from cache) 260 silly pacote range manifest for wcwidth@^1.0.1 fetched in 194ms 261 silly resolveWithNewModule wcwidth@1.0.1 checking installable status 262 http fetch GET 304 https://registry.npmjs.org/log-symbols 200ms (from cache) 263 silly pacote range manifest for log-symbols@^2.2.0 fetched in 201ms 264 silly resolveWithNewModule log-symbols@2.2.0 checking installable status 265 http fetch GET 304 https://registry.npmjs.org/restore-cursor 181ms (from cache) 266 silly pacote range manifest for restore-cursor@^2.0.0 fetched in 183ms 267 silly resolveWithNewModule restore-cursor@2.0.0 checking installable status 268 http fetch GET 304 https://registry.npmjs.org/onetime 171ms (from cache) 269 silly pacote range manifest for onetime@^2.0.0 fetched in 172ms 270 silly resolveWithNewModule onetime@2.0.1 checking installable status 271 http fetch GET 304 https://registry.npmjs.org/mimic-fn 180ms (from cache) 272 silly pacote range manifest for mimic-fn@^1.0.0 fetched in 180ms 273 silly resolveWithNewModule mimic-fn@1.2.0 checking installable status 274 http fetch GET 304 https://registry.npmjs.org/ansi-regex 191ms (from cache) 275 silly pacote range manifest for ansi-regex@^4.1.0 fetched in 191ms 276 silly resolveWithNewModule ansi-regex@4.1.0 checking installable status 277 http fetch GET 304 https://registry.npmjs.org/defaults 176ms (from cache) 278 silly pacote range manifest for defaults@^1.0.3 fetched in 177ms 279 silly resolveWithNewModule defaults@1.0.3 checking installable status 280 http fetch GET 304 https://registry.npmjs.org/clone 186ms (from cache) 281 silly pacote range manifest for clone@^1.0.2 fetched in 187ms 282 silly resolveWithNewModule clone@1.0.4 checking installable status 283 http fetch GET 304 https://registry.npmjs.org/parse-json 185ms (from cache) 284 http fetch GET 304 https://registry.npmjs.org/@types%2fnormalize-package-data 188ms (from cache) 285 http fetch GET 304 https://registry.npmjs.org/type-fest 186ms (from cache) 286 silly pacote range manifest for parse-json@^5.0.0 fetched in 187ms 287 silly resolveWithNewModule parse-json@5.0.0 checking installable status 288 silly pacote range manifest for @types/normalize-package-data@^2.4.0 fetched in 189ms 289 silly resolveWithNewModule @types/normalize-package-data@2.4.0 checking installable status 290 silly pacote range manifest for type-fest@^0.6.0 fetched in 189ms 291 silly resolveWithNewModule type-fest@0.6.0 checking installable status 292 http fetch GET 304 https://registry.npmjs.org/normalize-package-data 200ms (from cache) 293 silly pacote range manifest for normalize-package-data@^2.5.0 fetched in 202ms 294 silly resolveWithNewModule normalize-package-data@2.5.0 checking installable status 295 silly pacote range manifest for semver@2 || 3 || 4 || 5 fetched in 4ms 296 silly resolveWithNewModule semver@5.7.1 checking installable status 297 http fetch GET 304 https://registry.npmjs.org/hosted-git-info 168ms (from cache) 298 silly pacote range manifest for hosted-git-info@^2.1.4 fetched in 169ms 299 silly resolveWithNewModule hosted-git-info@2.8.5 checking installable status 300 http fetch GET 304 https://registry.npmjs.org/validate-npm-package-license 173ms (from cache) 301 silly pacote range manifest for validate-npm-package-license@^3.0.1 fetched in 173ms 302 silly resolveWithNewModule validate-npm-package-license@3.0.4 checking installable status 303 http fetch GET 304 https://registry.npmjs.org/path-parse 183ms (from cache) 304 silly pacote range manifest for path-parse@^1.0.6 fetched in 183ms 305 silly resolveWithNewModule path-parse@1.0.6 checking installable status 306 http fetch GET 304 https://registry.npmjs.org/spdx-expression-parse 175ms (from cache) 307 http fetch GET 304 https://registry.npmjs.org/spdx-correct 175ms (from cache) 308 silly pacote range manifest for spdx-expression-parse@^3.0.0 fetched in 176ms 309 silly resolveWithNewModule spdx-expression-parse@3.0.0 checking installable status 310 silly pacote range manifest for spdx-correct@^3.0.0 fetched in 177ms 311 silly resolveWithNewModule spdx-correct@3.1.0 checking installable status 312 http fetch GET 304 https://registry.npmjs.org/spdx-license-ids 175ms (from cache) 313 silly pacote range manifest for spdx-license-ids@^3.0.0 fetched in 176ms 314 silly resolveWithNewModule spdx-license-ids@3.0.5 checking installable status 315 http fetch GET 304 https://registry.npmjs.org/spdx-exceptions 172ms (from cache) 316 silly pacote range manifest for spdx-exceptions@^2.1.0 fetched in 173ms 317 silly resolveWithNewModule spdx-exceptions@2.2.0 checking installable status 318 http fetch GET 404 https://registry.npmjs.org/error-ex 166ms 319 http fetch GET 304 https://registry.npmjs.org/json-parse-better-errors 190ms (from cache) 320 silly pacote range manifest for json-parse-better-errors@^1.0.1 fetched in 191ms 321 silly resolveWithNewModule json-parse-better-errors@1.0.2 checking installable status 322 http fetch GET 304 https://registry.npmjs.org/lines-and-columns 192ms (from cache) 323 silly pacote range manifest for lines-and-columns@^1.1.6 fetched in 193ms 324 silly resolveWithNewModule lines-and-columns@1.1.6 checking installable status 325 http fetch GET 304 https://registry.npmjs.org/@babel%2fcode-frame 203ms (from cache) 326 silly pacote range manifest for @babel/code-frame@^7.0.0 fetched in 203ms 327 silly resolveWithNewModule @babel/code-frame@7.8.3 checking installable status 328 http fetch GET 404 https://registry.npmjs.org/error-ex 153ms 329 silly fetchPackageMetaData error for error-ex@^1.3.1 404 Not Found - GET https://registry.npmjs.org/error-ex 330 timing stage:rollbackFailedOptional Completed in 0ms 331 timing stage:runTopLevelLifecycles Completed in 8161ms 332 silly saveTree Sellist 332 silly saveTree └─┬ @vue/cli@4.2.2 332 silly saveTree ├─┬ @vue/cli-shared-utils@4.2.2 332 silly saveTree │ ├─┬ @hapi/joi@15.1.1 332 silly saveTree │ │ ├── @hapi/address@2.1.4 332 silly saveTree │ │ ├── @hapi/bourne@1.3.2 332 silly saveTree │ │ ├── @hapi/hoek@8.5.1 332 silly saveTree │ │ └── @hapi/topo@3.1.6 332 silly saveTree │ ├─┬ chalk@2.4.2 332 silly saveTree │ │ ├─┬ ansi-styles@3.2.1 332 silly saveTree │ │ │ └─┬ color-convert@1.9.3 332 silly saveTree │ │ │ └── color-name@1.1.3 332 silly saveTree │ │ ├── escape-string-regexp@1.0.5 332 silly saveTree │ │ └─┬ supports-color@5.5.0 332 silly saveTree │ │ └── has-flag@3.0.0 332 silly saveTree │ ├─┬ execa@1.0.0 332 silly saveTree │ │ ├─┬ cross-spawn@6.0.5 332 silly saveTree │ │ │ ├── nice-try@1.0.5 332 silly saveTree │ │ │ ├── path-key@2.0.1 332 silly saveTree │ │ │ ├── semver@5.7.1 332 silly saveTree │ │ │ ├─┬ shebang-command@1.2.0 332 silly saveTree │ │ │ │ └── shebang-regex@1.0.0 332 silly saveTree │ │ │ └─┬ which@1.3.1 332 silly saveTree │ │ │ └── isexe@2.0.0 332 silly saveTree │ │ ├─┬ get-stream@4.1.0 332 silly saveTree │ │ │ └─┬ pump@3.0.0 332 silly saveTree │ │ │ ├─┬ end-of-stream@1.4.4 332 silly saveTree │ │ │ │ └─┬ once@1.4.0 332 silly saveTree │ │ │ │ └── wrappy@1.0.2 332 silly saveTree │ │ │ └── once@1.4.0 332 silly saveTree │ │ ├── is-stream@1.1.0 332 silly saveTree │ │ ├── npm-run-path@2.0.2 332 silly saveTree │ │ ├── p-finally@1.0.0 332 silly saveTree │ │ ├── signal-exit@3.0.2 332 silly saveTree │ │ └── strip-eof@1.0.0 332 silly saveTree │ ├─┬ launch-editor@2.2.1 332 silly saveTree │ │ └── shell-quote@1.7.2 332 silly saveTree │ ├─┬ lru-cache@5.1.1 332 silly saveTree │ │ └── yallist@3.1.1 332 silly saveTree │ ├─┬ node-ipc@9.1.1 332 silly saveTree │ │ ├── event-pubsub@4.3.0 332 silly saveTree │ │ ├── js-message@1.0.5 332 silly saveTree │ │ └─┬ js-queue@2.0.0 332 silly saveTree │ │ └── easy-stack@1.0.0 332 silly saveTree │ ├─┬ open@6.4.0 332 silly saveTree │ │ └── is-wsl@1.1.0 332 silly saveTree │ ├─┬ ora@3.4.0 332 silly saveTree │ │ ├─┬ cli-cursor@2.1.0 332 silly saveTree │ │ │ └─┬ restore-cursor@2.0.0 332 silly saveTree │ │ │ └─┬ onetime@2.0.1 332 silly saveTree │ │ │ └── mimic-fn@1.2.0 332 silly saveTree │ │ ├── cli-spinners@2.2.0 332 silly saveTree │ │ ├── log-symbols@2.2.0 332 silly saveTree │ │ ├─┬ strip-ansi@5.2.0 332 silly saveTree │ │ │ └── ansi-regex@4.1.0 332 silly saveTree │ │ └─┬ wcwidth@1.0.1 332 silly saveTree │ │ └─┬ defaults@1.0.3 332 silly saveTree │ │ └── clone@1.0.4 332 silly saveTree │ ├─┬ read-pkg@5.2.0 332 silly saveTree │ │ ├── @types/normalize-package-data@2.4.0 332 silly saveTree │ │ ├─┬ normalize-package-data@2.5.0 332 silly saveTree │ │ │ ├── hosted-git-info@2.8.5 332 silly saveTree │ │ │ ├─┬ resolve@1.15.1 332 silly saveTree │ │ │ │ └── path-parse@1.0.6 332 silly saveTree │ │ │ ├── semver@5.7.1 332 silly saveTree │ │ │ └─┬ validate-npm-package-license@3.0.4 332 silly saveTree │ │ │ ├─┬ spdx-correct@3.1.0 332 silly saveTree │ │ │ │ ├─┬ spdx-expression-parse@3.0.0 332 silly saveTree │ │ │ │ │ ├── spdx-exceptions@2.2.0 332 silly saveTree │ │ │ │ │ └── spdx-license-ids@3.0.5 332 silly saveTree │ │ │ │ └── spdx-license-ids@3.0.5 332 silly saveTree │ │ │ └── spdx-expression-parse@3.0.0 332 silly saveTree │ │ ├─┬ parse-json@5.0.0 332 silly saveTree │ │ │ ├── @babel/code-frame@7.8.3 332 silly saveTree │ │ │ ├── json-parse-better-errors@1.0.2 332 silly saveTree │ │ │ └── lines-and-columns@1.1.6 332 silly saveTree │ │ └── type-fest@0.6.0 332 silly saveTree │ ├── request-promise-native@1.0.8 332 silly saveTree │ ├── request@2.88.2 332 silly saveTree │ ├── semver@6.3.0 332 silly saveTree │ └── strip-ansi@6.0.0 332 silly saveTree ├── @vue/cli-ui-addon-webpack@4.2.2 332 silly saveTree ├── @vue/cli-ui-addon-widgets@4.2.2 332 silly saveTree ├─┬ @vue/cli-ui@4.2.2 332 silly saveTree │ ├── deepmerge@4.2.2 332 silly saveTree │ ├── fs-extra@7.0.1 332 silly saveTree │ ├── globby@9.2.0 332 silly saveTree │ ├── javascript-stringify@1.6.0 332 silly saveTree │ ├── js-yaml@3.13.1 332 silly saveTree │ └── shortid@2.2.15 332 silly saveTree ├── boxen@4.2.0 332 silly saveTree ├── cmd-shim@3.0.3 332 silly saveTree ├── commander@2.20.3 332 silly saveTree ├── debug@4.1.1 332 silly saveTree ├── deepmerge@4.2.2 332 silly saveTree ├── didyoumean@1.2.1 332 silly saveTree ├── download-git-repo@1.1.0 332 silly saveTree ├── ejs@2.7.4 332 silly saveTree ├── envinfo@7.5.0 332 silly saveTree ├── fs-extra@7.0.1 332 silly saveTree ├── globby@9.2.0 332 silly saveTree ├── import-global@0.1.0 332 silly saveTree ├── inquirer@6.5.2 332 silly saveTree ├── isbinaryfile@4.0.4 332 silly saveTree ├── javascript-stringify@1.6.0 332 silly saveTree ├── js-yaml@3.13.1 332 silly saveTree ├─┬ jscodeshift@0.7.0 332 silly saveTree │ └── recast@0.18.5 332 silly saveTree ├── lodash.clonedeep@4.5.0 332 silly saveTree ├── lru-cache@5.1.1 332 silly saveTree ├── minimist@1.2.0 332 silly saveTree ├── recast@0.18.5 332 silly saveTree ├── resolve@1.15.1 332 silly saveTree ├── shortid@2.2.15 332 silly saveTree ├── slash@3.0.0 332 silly saveTree ├── validate-npm-package-name@3.0.0 332 silly saveTree ├── vue-jscodeshift-adapter@2.0.3 332 silly saveTree └── yaml-front-matter@3.4.1 333 verbose stack Error: 404 Not Found - GET https://registry.npmjs.org/error-ex 333 verbose stack at /usr/local/lib/node_modules/npm/node_modules/npm-registry-fetch/check-response.js:104:15 333 verbose stack at processTicksAndRejections (internal/process/task_queues.js:94:5) 334 verbose statusCode 404 335 verbose pkgid error-ex@^1.3.1 336 verbose cwd /Users/sellist/Projects/Sellist 337 verbose Darwin 18.7.0 338 verbose argv "/usr/local/Cellar/node@12/12.15.0/bin/node" "/usr/local/bin/npm" "install" "@vue/cli" 339 verbose node v12.15.0 340 verbose npm v6.13.7 341 error code E404 342 error 404 Not Found - GET https://registry.npmjs.org/error-ex 343 error 404 344 error 404 'error-ex@^1.3.1' is not in the npm registry. 345 error 404 You should bug the author to publish it (or use the name yourself!) 346 error 404 It was specified as a dependency of 'parse-json' 347 error 404 Note that you can also install from a 348 error 404 tarball, folder, http url, or git url. 349 verbose exit [ 1, true ]

closed time in 14 days

awmed

issue commentvuejs/vue-cli

Unable to install @vue/cli or install dependecies

Hello, thank you for taking time filling this issue!

However, we kindly ask you to use our Issue Helper when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatically closed by me (your robot friend!).

I hope to see your helper-created issue very soon!

awmed

comment created time in 14 days

issue closedvuejs/vue-devtools

npm run build报错

leguan@leguandeMacBook-Pro vue-devtools % npm run build

vue-devtools@5.3.3 build /Users/leguan/Desktop/dectools/vue-devtools cd packages/shell-chrome && cross-env NODE_ENV=production webpack --progress --hide-modules

events.js:298 throw er; // Unhandled 'error' event ^ Error: spawn webpack ENOENT at Process.ChildProcess._handle.onexit (internal/child_process.js:267:19) at onErrorNT (internal/child_process.js:467:16) at processTicksAndRejections (internal/process/task_queues.js:84:21) Emitted 'error' event on ChildProcess instance at: at Process.ChildProcess._handle.onexit (internal/child_process.js:273:12) at onErrorNT (internal/child_process.js:467:16) at processTicksAndRejections (internal/process/task_queues.js:84:21) { errno: -2, code: 'ENOENT', syscall: 'spawn webpack', path: 'webpack', spawnargs: [ '--progress', '--hide-modules' ] } npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! vue-devtools@5.3.3 build: cd packages/shell-chrome && cross-env NODE_ENV=production webpack --progress --hide-modules npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the vue-devtools@5.3.3 build script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above. npm ERR! A complete log of this run can be found in: npm ERR! /Users/leguan/.npm/_logs/2020-02-11T10_00_31_261Z-debug.log

closed time in 15 days

1067831145

issue commentvuejs/vue-devtools

npm run build报错

Hello, thank you for taking time filling this issue!

However, we kindly ask you to use our Issue Helper when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatically closed by me (your robot friend!).

I hope to see your helper-created issue very soon!

1067831145

comment created time in 15 days

issue closedvuejs/rollup-plugin-vue

Dynamic import vue components

Is there a wait to pass on options of Vue.use() the name of components and dynamically import them? I'm trying it but the normalizeComponent is just applied to imported components as:

import TextImage from '../src/components/modules/TextImage.vue';

let component = Object.values(await import('../src/components/modules/TextImage.vue'))[0];
    if (options.modules) {
      options.modules.map(async moduleName => {
        Vue.component(moduleName, component);
    });
}

closed time in 16 days

rpvsilva

issue commentvuejs/rollup-plugin-vue

Dynamic import vue components

Hello, thank you for taking time filling this issue!

However, we kindly ask you to use our Issue Helper when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatically closed by me (your robot friend!).

I hope to see your helper-created issue very soon!

rpvsilva

comment created time in 16 days

issue closedvuejs/vue

Error when return html character to japanese

I have a string &#20986;&#21253;&#29579;&#22899;&#32;&#26263;&#32;. It will be auto convert to "出包王女 暗" when I use below code: <h2>&#20986;&#21253;&#29579;&#22899;&#32;&#26263;&#32;</h2>

But when I use vuejs code as folowing: data = "&#20986;&#21253;&#29579;&#22899;&#32;&#26263;&#32;" <h2>{{ data }}</h2> => It can not display right text "出包王女 暗". It was displayed &#20986;&#21253;&#29579;&#22899;&#32;&#26263;&#32;

So, How to auto convert &#20986;&#21253;&#29579;&#22899;&#32;&#26263;&#32; to 出包王女 暗 ? I don't want to convert by manual. Thanks!

closed time in 16 days

gemtcn

issue commentvuejs/vue

Error when return html character to japanese

Hello, thank you for taking time filling this issue!

However, we kindly ask you to use our Issue Helper when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatically closed by me (your robot friend!).

I hope to see your helper-created issue very soon!


你好,你的 issue 不符合我们所要求的格式,因此已被自动关闭。为了确保每个 issue 都提供必需的相关信息,请务必使用我们的 Issue 向导 来创建新 issue,谢谢!

gemtcn

comment created time in 16 days

issue closedvuejs/vue

Why so shitty support?

I hate to spend 5 minutes to register every time for 1 question on your different forums which will maybe receive an answer in 10 years after it was asked.

Why so shitty support from the community? Why you do not use git for issues like everyone who respects their client's time do?

closed time in 17 days

BonBonSlick

issue commentvuejs/vue

Why so shitty support?

Hello, thank you for taking time filling this issue!

However, we kindly ask you to use our Issue Helper when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatically closed by me (your robot friend!).

I hope to see your helper-created issue very soon!

BonBonSlick

comment created time in 17 days

issue closedvuejs/vue

$http.delete with warning "avoid using JavaScript unary operator as property name"

Version

2.6.11

Reproduction link

https://codepen.io/frOracle/pen/vYOEEVW

Steps to reproduce

use $http.delete in @click

What is expected?

$http.delete is a function, not unary operator

What is actually happening?

a warning "avoid using JavaScript unary operator as property name"

Related

https://github.com/vuejs/vue/issues/5464

closed time in 19 days

frOracle

issue commentvuejs/vue

$http.delete with warning "avoid using JavaScript unary operator as property name"

Hello, thank you for taking time filling this issue!

However, we kindly ask you to use our Issue Helper when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatically closed by me (your robot friend!).

I hope to see your helper-created issue very soon!

frOracle

comment created time in 19 days

issue closedvuejs/vue-cli

WOah

IMPORTANT: Please use the following link to create a new issue:

https://new-issue.vuejs.org/?repo=vuejs/vue-cli

If your issue was not created using the app above, it will be closed immediately.

中文用户请注意: 请使用上面的链接来创建新的 issue。如果不是用上述工具创建的 issue 会被自动关闭。

closed time in 20 days

20whiting

issue commentvuejs/vue-cli

WOah

Hello, thank you for taking time filling this issue!

However, we kindly ask you to use our Issue Helper when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatically closed by me (your robot friend!).

I hope to see your helper-created issue very soon!


你好,你的 issue 不符合我们所要求的格式,因此已被自动关闭。为了确保每个 issue 都提供必需的相关信息,请务必使用我们的 Issue 向导 来创建新 issue,谢谢!

20whiting

comment created time in 20 days

issue closedvuejs/vue-router

Using named target using router-link

Right now, if we want to open a link in a new tab (or page), we can use target="_blank".

In some cases, I prefer using named target when opening a new tab. This way, if we click multiple times on the same link, it will only refresh the named tab already opened.

Accepting something like target="my_report" would be great. Right now, the target attribute is added to the a tag, but the link is not opened on another tab.

closed time in 20 days

service-paradis

issue commentvuejs/vue-router

Using named target using router-link

Hello, thank you for taking time filling this issue!

However, we kindly ask you to use our Issue Helper when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatically closed by me (your robot friend!).

I hope to see your helper-created issue very soon!

service-paradis

comment created time in 20 days

issue closedvuejs/vue-cli

Error: No module factory available for dependency type: CssDependency

Version 4.1.0

Issue This week I started to learn Vue CLI and when I try to Build my Web App the following error appears in the Output of the vue ui:

Error: No module factory available for dependency type: CssDependency

I'm quite new to this and I don't quite understand why this happens, even because when I do the "run serve", the Web App works on localhost.

I spoke with a friend of mine at college and he told me to install a few depencies, such as mini-css-extract-plugin, vue-style-loader and css-loader. But it did not work.

package.json

{ "name": "vuewebapp", "version": "0.1.0", "private": true, "scripts": { "serve": "vue-cli-service serve", "build": "vue-cli-service build", "lint": "vue-cli-service lint" }, "dependencies": { "animate.css": "^3.7.2", "bulma": "^0.8.0", "core-js": "^3.4.4", "css-loader": "^3.4.2", "mini-css-extract-plugin": "^0.9.0", "vue": "^2.6.10", "vue-router": "^3.1.3", "vue-style-loader": "^4.1.2" }, "devDependencies": { "@vue/cli-plugin-babel": "^4.1.0", "@vue/cli-plugin-eslint": "^4.1.0", "@vue/cli-plugin-router": "^4.1.0", "@vue/cli-service": "^4.1.0", "babel-eslint": "^10.0.3", "eslint": "^5.16.0", "eslint-plugin-vue": "^5.0.0", "node-sass": "^4.12.0", "sass-loader": "^8.0.0", "vue-template-compiler": "^2.6.10" }, "eslintConfig": { "root": true, "env": { "node": true }, "extends": [ "plugin:vue/essential", "eslint:recommended" ], "rules": {}, "parserOptions": { "parser": "babel-eslint" } }, "browserslist": [ "> 1%", "last 2 versions" ] }

closed time in 20 days

FranciscoMendes10866

issue commentvuejs/vue-cli

Error: No module factory available for dependency type: CssDependency

Hello, thank you for taking time filling this issue!

However, we kindly ask you to use our Issue Helper when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatically closed by me (your robot friend!).

I hope to see your helper-created issue very soon!

FranciscoMendes10866

comment created time in 20 days

create barnchvuejs/vue

branch : patreon-update-1580897300832

created branch time in 21 days

PR opened vuejs/vue

[automated] Patreon sponsors update

This is an automated pull request.

+18 -8

0 comment

2 changed files

pr created time in 21 days

create barnchvuejs/vuejs.org

branch : patreon-update-1580897300832

created branch time in 21 days

PR opened vuejs/vuejs.org

[automated] Patreon sponsors update

This is an automated pull request.

+6 -3

0 comment

2 changed files

pr created time in 21 days

issue closedvuejs/vue-cli

[Question][Need help] What is these files after builded?

Screen Shot 2020-02-05 at 11 57 05 AM

could you tell me what is these files after builded? is it redundancy file? how can we remove it?

this is vue.config.js file

`const { BundleAnalyzerPlugin } = require('webpack-bundle-analyzer'); const CompressionPlugin = require('compression-webpack-plugin');

const webpack = require('webpack');

const plugins = [new webpack.ContextReplacementPlugin(/moment[/\]locale$/, /en|vi/)];

if (process.env.NODE_ENV !== 'production') { plugins.push(new BundleAnalyzerPlugin()); }

module.exports = { productionSourceMap: false, configureWebpack: { plugins, performance: { maxEntrypointSize: 512000, maxAssetSize: 512000, }, }, chainWebpack(config) { config.plugins.delete('prefetch'); config.plugin('CompressionPlugin').use(CompressionPlugin); }, }; `

closed time in 21 days

PhuHoaframgia

issue commentvuejs/vue-cli

[Question][Need help] What is these files after builded?

Hello, thank you for taking time filling this issue!

However, we kindly ask you to use our Issue Helper when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatically closed by me (your robot friend!).

I hope to see your helper-created issue very soon!

PhuHoaframgia

comment created time in 21 days

create barnchvuejs/vue

branch : patreon-update-1580878815334

created branch time in 21 days

create barnchvuejs/vue

branch : patreon-update-1580878823783

created branch time in 21 days

PR opened vuejs/vue

[automated] Patreon sponsors update

This is an automated pull request.

+8 -8

0 comment

2 changed files

pr created time in 21 days

create barnchvuejs/vuejs.org

branch : patreon-update-1580878823783

created branch time in 21 days

PR opened vuejs/vuejs.org

[automated] Patreon sponsors update

This is an automated pull request.

+3 -3

0 comment

1 changed file

pr created time in 21 days

PR opened vuejs/vue

[automated] Patreon backers update (Feb 2020

This is an automated pull request.

+16 -24

0 comment

1 changed file

pr created time in 21 days

issue closedvuejs/vue

动态组件插入相同组件,splice失效,都成了push

循环的动态组件 <component :is="item" :key="item.index" v-for="(item,index) in leftContent">${ item }</component> 插入动态组件(每次插入的组件都是ParagraphPreview组件) this.$parent.leftContent.splice(this.itemIdx, 0, 'ParagraphPreview'); 插入位置没有按照指定位置插入,都插入到了动态组件的最后

closed time in 21 days

Better-Self

issue commentvuejs/vue

动态组件插入相同组件,splice失效,都成了push

Hello, thank you for taking time filling this issue!

However, we kindly ask you to use our Issue Helper when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatically closed by me (your robot friend!).

I hope to see your helper-created issue very soon!


你好,你的 issue 不符合我们所要求的格式,因此已被自动关闭。为了确保每个 issue 都提供必需的相关信息,请务必使用我们的 Issue 向导 来创建新 issue,谢谢!

Better-Self

comment created time in 21 days

create barnchvuejs/vue

branch : patreon-update-1580844808555

created branch time in 22 days

PR opened vuejs/vue

[automated] Patreon sponsors update

This is an automated pull request.

+15 -0

0 comment

2 changed files

pr created time in 22 days

create barnchvuejs/vuejs.org

branch : patreon-update-1580844808555

created branch time in 22 days

PR opened vuejs/vuejs.org

[automated] Patreon sponsors update

This is an automated pull request.

+3 -0

0 comment

2 changed files

pr created time in 22 days

issue closedvuejs/vue-cli

Installing CLI plugins. taking too much time get download. i

Version Vue CLI v4.1.2

Steps to reproduce Use commands in console: sudo npm install -g vue sudo npm install -g @vue/cli Then: sudo Screenshot from 2020-02-04 22-36-37 vue create mpproj

What is expected? The project "mpproj" was created.

What is actually happening? After choosing parameters this text was showing in console for endless time : Vue CLI v4.1.2 ✨ Creating project in /home/vikash/mpproj. ⚙ Installing CLI plugins. This might take a while...

loadDep:jsesc -> network - |##########################################################---------------------------------------------------------------------------------------------------------------------| { "name": "mpproj", "version": "0.1.0", "private": true, "devDependencies": { "@vue/cli-plugin-babel": "^4.1.0", "@vue/cli-plugin-eslint": "^4.1.0", "@vue/cli-service": "^4.1.0" } }

closed time in 22 days

vikashRG

issue commentvuejs/vue-cli

Installing CLI plugins. taking too much time get download. i

Hello, thank you for taking time filling this issue!

However, we kindly ask you to use our Issue Helper when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatically closed by me (your robot friend!).

I hope to see your helper-created issue very soon!

vikashRG

comment created time in 22 days

issue closedvuejs/vue

Test

After the introduction of the new API (written in python) the calls no longer work. The new api can be found here: GraphQL API

Love vuejs? Please consider supporting us via Patreon or OpenCollective: 👉 https://www.patreon.com/evanyou 👉 https://opencollective.com/vuejs/donate

closed time in 22 days

alitaassofnm

issue commentvuejs/vue

Test

Hello, thank you for taking time filling this issue!

However, we kindly ask you to use our Issue Helper when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatically closed by me (your robot friend!).

I hope to see your helper-created issue very soon!

alitaassofnm

comment created time in 22 days

more