Version

3.0.0-rc.10

Node and OS info

Node 8.11.2 / Yarn 1.7.0 / Windows 10

Steps to reproduce

• git clone https://github.com/vinaybedre/vue-cli-3-hmr-bug
• yarn install
• npm start serve
• Open server at http://localhost:8080/about
• Do changes to any src file eg. under views/About.vue change the text
• Under browser's console, I get error Failed to load resource: net::ERR_CONNECTION_TIMED_OUT
• HMR is not working as expected and mentioned

What is expected?

HMR should update the browser's content based on changes made on src file

What is actually happening?

HMR is failing, any changes done to the src files are not being hot reloaded in browser.

Any chance for an official typescript template?

when runing dev-server there throw these two Error

ERROR Failed to compile with 2 errors 10:53:28

These relative modules were not found:

• ./build/dev-client in multi ./build/dev-client ./src/main.js
• ./src/main.js in multi ./build/dev-client ./src/main.js

Listening at http://localhost:8080

node-version 6.8.0 window10 i don't modify the webpack default config, it can run the app sometime but mostly throw the error

We have been discussing an upgrade for vue-cli for a while, in order to address a few issues in the current version.

Problems

1. Currently, project build configurations are directly included in the template. This leads to a few problems:

   • once created, it becomes difficult to upgrade an existing project to track latest changes in the remote template;

   • pulling directly from github lacks proper version control mechanism that npm packages have;

   • less experienced users can get intimidated by the seemingly complex code in the build directory.

2. Too many decisions to make upfront resulting in a less smooth onboarding experience.

   The user has to first pick a template, but for beginners they usually do not possess the experience to decide which template fits their use case best. The official webpack template has a number of questions regarding linters and test tools, which can also be intimidating for beginners.

Solutions

1. [email protected] will be moving towards a "config/scripts in a package" model, which is commonly used among several other tools:

   • create-react-app
   • Next.js
   • Nuxt.js
   • Poi

2. Instead of forcing users to make non-reversible decisions upfront, we would:

   • Phase out browserify support. There will be just one template which is webpack based.

   • Configurations for common use cases (pwa, ts, ssr) can be added on demand via presets, similar to how Neutrino/Poi works. The presets can be maintained and versioned individually.

3. In addition to the encapsulated package, we will also offer the ability to configure the tooling via vue.config.js. This file exposes two functionalities:

   1. A centralized entry for configuring/toggling high-level built-in features, e.g. env variables, css extraction, API proxying.

   2. Get lower level access to the underlying webpack config and tweak it (probably with webpack-chain). This essentially works like a local preset.

Other Ideas

• We will probably split out vue build into an addon (e.g. vue-cli-build) so the initial install of vue-cli can be faster. vue build can simply try to call vue-cli-build, and prompt installation if it is not found.

• vue list will be deprecated, OR list available presets instead.

• Default integration of vue-test-utils and probably Jest as the runner (although it can lead to license concerns)

• Better error reporting, e.g. jumping directly to source code from error overlay.

• Grep for common warning / error messages and suggest potential doc links.

• Auto port detection (suggested by @billyryanwill)

• Your idea here

I realize this is in fact very similar to Poi and since @egoist has been an active contributor to vue-cli itself, I would love to get feedback from @egoist and potentially collaborate with him to build the new version. Maybe we can even build this on top of a fork of Poi?

/cc @vuejs/collaborators

Version

3.1.1

Node and OS info

npm 6.4.1

Steps to reproduce

npm install -g @vue/cli

What is expected?

Install Successful

What is actually happening?

npm WARN [email protected] requires a peer of [email protected]^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of [email protected]^0.10.5 || ^0.11.3 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of [email protected]^0.10.5 || ^0.11.3 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of [email protected]^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN @apollographql/[email protected] requires a peer of [email protected]^0.13.1 but none is installed. You must install peer dependencies yourself.

Even after I manually install graphql with npm install -g [email protected]^0.13.1, when I do npm -g list --depth=0, npm still warns

npm ERR! peer dep missing: [email protected]^0.11.0 || ^0.12.0 || ^0.13.0, required by [email protected]
npm ERR! peer dep missing: [email protected]^0.13.1, required by @apollographql/[email protected]
npm ERR! peer dep missing: [email protected]^0.10.5 || ^0.11.3 || ^0.12.0 || ^0.13.0, required by [email protected]
npm ERR! peer dep missing: [email protected]^0.13.0, required by [email protected]
npm ERR! peer dep missing: [email protected]^0.13.1, required by @apollographql/[email protected]
npm ERR! peer dep missing: [email protected]^0.10.5 || ^0.11.3 || ^0.12.0 || ^0.13.0, required by [email protected]
npm ERR! peer dep missing: [email protected]^0.13.0, required by [email protected]

Version

3.0.1

Node and OS info

nvm 0.33.1 / Node v8.11.4 / Ubuntu 16.04

Steps to reproduce

npm run build fails because vue-cli-service: command not found

What is expected?

npm run build succeeds

What is actually happening?

npm run build fails because vue-cli-service: command not found

Installed globally with npm install -g @vue/[email protected]

Version

3.0.0-alpha.13

Reproduction link

http://www.heyui.top/

Steps to reproduce

npm create test1
Please pick a preset: default (babel, eslint)

What is expected?

create successfull

What is actually happening?

ERROR command failed: npm install --loglevel error --registry=https://registry.npm.taobao.org --disturl=https://npm.taobao.org/dist

I choosed taobao registry, I can't change anymore.

It's time for a major version bump. This will be a relatively small release but will include a number of necessary breaking changes.

Planned Features

Dependency Updates

• [x] webpack-chain v5 (#3913) CHANGELOG
• [x] css-loader v2 (#3866) CHANGELOG
• [x] copy-webpack-plugin v5 CHANGELOG (a very subtle change, unless you've touched its options in config there won't be any affect)
• [x] Nightwatch v1 (#3388) MIGRATION GUIDE
• [x] Use ESLint v5 by default (#3775) (projects scaffolded with Vue CLI 3.1+ are already using it, for those scaffolded by 3.0.x, here's the migration guide for eslint and release note of eslint-plugin-vue v5)
• [x] Jest v24 (#3870) RELEASE NOTE
• [x] workbox v4 (#3915) RELEASE NOTE and MIGRATION GUIDE
• [x] core-js 3 (#3912) (It's an internal change of @vue/babel-preset/app, for now we use core-js 2 by default, babel 7.4.0 supports core-js 3, once we upgraded core-js, some undocumented public APIs may change)

Changed Behavior

• [x] vue-template-loader: preserveWhitespace: false -> whitespace: 'condense' #3853
• [x] use NODE_ENV=production by default if not specified when running vue-cli-service build #3859
• [x] plugin-pwa: manifest.json should be generated during the build process rather than scaffolding #2981

New Features

Most proposed new features other than plugin APIs can also be landed in v3.x so they are not listed here.

• [x] Plugin API: Allow plugins to provide a minimum vue-cli version #3861
• [x] vue upgrade overhaul, allowing running codemods from plugins
• [ ] Plugin ordering #1754, #1938

Removed

• [ ] Drop Node.js v9 support (in documentation, no need to touch the code)
• [x] remove support for vue-cli-service e2e command (already deprecated since 3.0 rc) (#3774)

Needs Discussion

• [ ] Drop unit mocha in favor of Jest only
  • Mostly because mocha-webpack is unmaintained and unlikely to work with webpack 5
  • Need good migration strategy for existing users
• [x] Use mochapack instead of mocha-webpack
• [x] Upgrade to mocha v6

How Can I Help?

Please let us know your thoughts and if we missed anything. We'll be more than happy to explain our rationale around these decisions if there's any further questions.

If there's anything you (and the community) feel strongly about but is not found on this list, please make an effort to send a PR! We'll be more than happy to accept contributions.

Version

Reproduction link

https://jsfiddle.net/b5u87965/

Steps to reproduce

when create a new vue project:

vue init webpack my-project

vue-cli · Failed to download repo vuejs-templates/webpack: read ECONNRESET

What is expected?

init a new vue project

What is actually happening?

vue-cli · Failed to download repo vuejs-templates/webpack: read ECONNRESET

Version

3.9.0

Environment info

Environment Info:

  System:
    OS: macOS Sierra 10.12.6
    CPU: (4) x64 Intel(R) Core(TM) i5-6287U CPU @ 3.10GHz
  Binaries:
    Node: 10.15.3 - ~/.nvm/versions/node/v10.15.3/bin/node
    Yarn: 1.13.0 - /usr/local/bin/yarn
    npm: 6.4.1 - ~/.nvm/versions/node/v10.15.3/bin/npm
  Browsers:
    Chrome: 75.0.3770.100
    Firefox: 67.0.4
    Safari: 12.1.1
  npmPackages:
    @vue/babel-helper-vue-jsx-merge-props:  1.0.0 
    @vue/babel-plugin-transform-vue-jsx:  1.0.0 
    @vue/babel-preset-app:  3.9.0 
    @vue/babel-preset-jsx:  1.0.0 
    @vue/babel-sugar-functional-vue:  1.0.0 
    @vue/babel-sugar-inject-h:  1.0.0 
    @vue/babel-sugar-v-model:  1.0.0 
    @vue/babel-sugar-v-on:  1.0.0 
    @vue/cli-overlay:  3.9.0 
    @vue/cli-plugin-babel: ^3.9.0 => 3.9.0 
    @vue/cli-plugin-eslint: ^3.9.0 => 3.9.0 
    @vue/cli-service: ^3.9.0 => 3.9.0 
    @vue/cli-shared-utils:  3.9.0 
    @vue/component-compiler-utils:  2.6.0 
    @vue/preload-webpack-plugin:  1.1.0 
    @vue/web-component-wrapper:  1.2.0 
    eslint-plugin-vue: ^5.0.0 => 5.2.3 (4.7.1)
    vue: ^2.6.10 => 2.6.10 
    vue-eslint-parser:  2.0.3 (5.0.0)
    vue-hot-reload-api:  2.3.3 
    vue-loader:  15.7.0 
    vue-router: ^3.0.3 => 3.0.7 
    vue-style-loader:  4.1.2 
    vue-template-compiler: ^2.6.10 => 2.6.10 
    vue-template-es2015-compiler:  1.9.1 
    vuex: ^3.0.1 => 3.1.1 
  npmGlobalPackages:
    @vue/cli: 3.9.0

Steps to reproduce

>vue create new-app
>cd new-app
>npm run serve

What is expected?

INFO  Starting development server...
 98% after emitting CopyPlugin                                                .  
 DONE  Compiled successfully in 3435ms                               10:02:58 AM

 
  App running at:
  - Local:   http://localhost:8080/ 
  - Network: http://10.145.82.231:8080/

  Note that the development build is not optimized.
  To create a production build, run npm run build.

What is actually happening?

INFO  Starting development server...
 98% after emitting CopyPlugin                                                 

 ERROR  Failed to compile with 1 errors                               9:53:57 AM

Module build failed (from ./node_modules/eslint-loader/index.js):
Error: Cannot find module '.../node_modules/eslint/lib/api.js/package.json'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:582:15)
    at Function.Module._load (internal/modules/cjs/loader.js:508:25)
    at Module.require (internal/modules/cjs/loader.js:637:17)
    at require (internal/modules/cjs/helpers.js:22:18)
    at Object.module.exports (.../node_modules/eslint-loader/index.js:170:23)

You may use special comments to disable some warnings.
Use // eslint-disable-next-line to ignore the next line.
Use /* eslint-disable */ to ignore all warnings in a file.

This is from a clean instantiation of a vue-cli application. No additional configuration to webpack or eslint. It had been working previously, so I'm thinking it could be a issue caused by a minor update to a dependency. Somewhere eslint-loader is getting a user defined eslint package path that does not exist.

Version

4.5.0

Environment info

Environment Info:

  System:
    OS: Windows 10 10.0.19042
    CPU: (8) x64 Intel(R) Core(TM) i7-4720HQ CPU @ 2.60GHz
  Binaries:
    Node: 12.16.3 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.5 - C:\ENVIRONMENT\yarn\bin\yarn.CMD
    npm: 6.14.11 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: 91.0.4472.164
    Edge: Spartan (44.19041.1023.0), Chromium (92.0.902.55)
  npmPackages:
    @vue/babel-helper-vue-jsx-merge-props:  1.2.1
    @vue/babel-helper-vue-transform-on:  1.0.2
    @vue/babel-plugin-jsx:  1.0.6
    @vue/babel-plugin-transform-vue-jsx:  1.2.1
    @vue/babel-preset-app:  4.5.13
    @vue/babel-preset-jsx:  1.2.4
    @vue/babel-sugar-composition-api-inject-h:  1.2.1
    @vue/babel-sugar-composition-api-render-instance:  1.2.4
    @vue/babel-sugar-functional-vue:  1.2.2
    @vue/babel-sugar-inject-h:  1.2.2
    @vue/babel-sugar-v-model:  1.2.3
    @vue/babel-sugar-v-on:  1.2.3
    @vue/cli-overlay:  4.5.13
    @vue/cli-plugin-babel: ^4.5.13 => 4.5.13
    @vue/cli-plugin-eslint: ~4.5.0 => 4.5.13
    @vue/cli-plugin-router: ~4.5.0 => 4.5.13
    @vue/cli-plugin-typescript: ~4.5.0 => 4.5.13
    @vue/cli-plugin-vuex: ~4.5.0 => 4.5.13
    @vue/cli-service: ~4.5.0 => 4.5.13
    @vue/cli-shared-utils:  4.5.13
    @vue/component-compiler-utils:  3.2.2
    @vue/composition-api: ^1.0.4 => 1.0.4
    @vue/eslint-config-prettier: ^6.0.0 => 6.0.0
    @vue/eslint-config-typescript: ^7.0.0 => 7.0.0
    @vue/preload-webpack-plugin:  undefined (1.1.2)
    @vue/web-component-wrapper:  1.3.0
    eslint-plugin-vue: ^7.4.1 => 7.4.1
    typescript: ^4.3.5 => 4.3.5
    vue: 2.6.12 => 2.6.12
    vue-awesome: ^2.3.3 => 2.3.8
    vue-class-component: ^7.2.6 => 7.2.6
    vue-cli: ^2.9.6 => 2.9.6
    vue-eslint-parser:  7.9.0 (7.3.0)
    vue-hot-reload-api:  2.3.4
    vue-loader: ^13.0.4 => 13.7.3 (16.3.3, 15.9.6)
    vue-qr: ^1.2.3 => 1.5.3
    vue-router: ^2.7.0 => 2.8.1
    vue-style-loader: ^3.0.1 => 3.1.2 (4.1.3)
    vue-template-compiler: 2.6.12 => 2.6.12
    vue-template-es2015-compiler:  1.9.1
    vuedraggable: ^2.16.0 => 2.24.3
    vuex: ^3.6.2 => 3.6.2
  npmGlobalPackages:
    @vue/cli: Not Found

Steps to reproduce

<template>
	<div id="app">
		<router-view></router-view>
	</div>
</template>
<script lang="ts">
import Vue from 'vue';
export default class App extends Vue {
	count = 0;
}
</script>

and then got this error

 ERROR  Failed to compile with 1 error                                                                                                                 
 error  in ./src/App.vue?vue&type=script&lang=ts&

Syntax Error: Unexpected token (3:10)

  1 | import Vue from 'vue';
  2 | export default class App extends Vue {
> 3 |     count = 0;
    |           ^
  4 | }
  5 | 



 @ ./src/App.vue?vue&type=script&lang=ts& 1:0-446 1:462-465 1:467-910 1:467-910
 @ ./src/App.vue
 @ ./src/main.ts
 @ multi (webpack)-dev-server/client?http://192.168.31.172:9005&sockPath=/sockjs-node (webpack)/hot/dev-server.js ./src/main.ts

No type errors found
Version: typescript 4.3.5

FYI , if I remove lang="ts" and then there is no errors

What is expected?

ts of js should be the same

What is actually happening?

on lang="ts" will got syntax error , but no on js

if update vue to 2.6.13 will got a parser error witch tells me to install vue-template-compiler

ERROR Failed to compile with 1 error
Syntax Error: TypeError: Cannot read property 'parseComponent' of undefined

You may use special comments to disable some warnings. Use // eslint-disable-next-line to ignore the next line. Use /* eslint-disable */ to ignore all warnings in a file. INTERNAL ERROR(undefined,undefined) When you use vue option, make sure to install vue-template-compiler.

this project was ran as js all the time, back then it was webpack underneath, recently I want to use vue-cli-service to replace original webpack&express , and it works just fine with *.ts file, not on vue with lang='ts' file, It confuse me , and I can't found any solution but wirte this bug report hoping you guys can help me out. Thanks a lot.

The produced demo page should at least be mentioned in the docs

What kind of change does this PR introduce? (check at least one)

• [ ] Bugfix
• [ ] Feature
• [ ] Code style update
• [ ] Refactor
• [x] Docs
• [ ] Underlying tools
• [ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

• [ ] Yes
• [x] No

Other information: The library build target documentation does not mention the fact a demo.html file is created during build, I feel it should be.

Version

4.5.13

Reproduction link

https://github.com/Bible-Projects/believers-sword-app

Environment info

  System:
    OS: Windows 10 10.0.19043
    CPU: (8) x64 Intel(R) Core(TM) i5-10300H CPU @ 2.50GHz   
  Binaries:
    Node: 14.16.1 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.10 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 7.19.1 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: Not Found
    Edge: Spartan (44.19041.1023.0), Chromium (91.0.864.71)  
  npmPackages:
    @css-render/vue3-ssr:  0.15.4
    @vue/babel-helper-vue-jsx-merge-props:  1.2.1
    @vue/babel-helper-vue-transform-on:  1.0.2
    @vue/babel-plugin-jsx:  1.0.6
    @vue/babel-plugin-transform-vue-jsx:  1.2.1
    @vue/babel-preset-app:  4.5.13
    @vue/babel-preset-jsx:  1.2.4
    @vue/babel-sugar-composition-api-inject-h:  1.2.1        
    @vue/babel-sugar-composition-api-render-instance:  1.2.4 
    @vue/babel-sugar-functional-vue:  1.2.2
    @vue/babel-sugar-inject-h:  1.2.2
    @vue/babel-sugar-v-model:  1.2.3
    @vue/babel-sugar-v-on:  1.2.3
    @vue/cli-overlay:  4.5.13
    @vue/cli-plugin-babel: ~4.5.0 => 4.5.13
    @vue/cli-plugin-eslint: ~4.5.0 => 4.5.13
    @vue/cli-plugin-pwa: ~4.5.0 => 4.5.13
    @vue/cli-plugin-router: ~4.5.0 => 4.5.13
    @vue/cli-plugin-typescript: ~4.5.0 => 4.5.13
    @vue/cli-plugin-vuex: ~4.5.0 => 4.5.13
    @vue/cli-service: ~4.5.0 => 4.5.13
    @vue/cli-shared-utils:  4.5.13
    @vue/compiler-core:  3.1.5
    @vue/compiler-dom:  3.1.5
    @vue/compiler-sfc: ^3.0.0 => 3.1.5
    @vue/compiler-ssr:  3.1.5
    @vue/component-compiler-utils:  3.2.2
    @vue/devtools-api:  6.0.0-beta.15
    @vue/eslint-config-prettier: ^6.0.0 => 6.0.0
    @vue/eslint-config-typescript: ^7.0.0 => 7.0.0
    @vue/preload-webpack-plugin:  1.1.2
    @vue/reactivity:  3.1.5
    @vue/runtime-core:  3.1.5
    @vue/runtime-dom:  3.1.5
    @vue/shared:  3.1.5
    @vue/web-component-wrapper:  1.3.0
    eslint-plugin-vue: ^7.0.0 => 7.13.0
    typescript: ~4.1.5 => 4.1.6
    vue: ^3.0.0 => 3.1.5
    vue-cli-plugin-electron-builder: ~2.1.1 => 2.1.1
    vue-eslint-parser:  7.8.0
    vue-hot-reload-api:  2.3.4
    vue-loader:  15.9.7 (16.3.1)
    vue-router: ^4.0.0-0 => 4.0.10
    vue-style-loader:  4.1.3
    vue-template-es2015-compiler:  1.9.1
    vueuc:  0.4.9
    vuex: ^4.0.0-0 => 4.0.2
  npmGlobalPackages:
    @vue/cli: Not Found

Steps to reproduce

running

cross-env WEB=1 vue-cli-service build --dest /../sampleouput/public/front

does not work.. I would like to move the output from different directory

What is expected?

Their should be a new Folder called sampleoutput/public/front from cd ..

What is actually happening?

nothing is being outputed in cd ..

1. I don't think I'll ever have the capacity to keep maintaining this compat plugin. It's better to drop it now than later.
2. The plugin is needed at the time of alpha.0 because many ecosystem plugins did not support webpack 5. But now I don't think it will be a major hurdle.
3. The implementation was too hacky.

What kind of change does this PR introduce? (check at least one)

• [ ] Bugfix
• [ ] Feature
• [ ] Code style update
• [x] Refactor
• [ ] Docs
• [ ] Underlying tools
• [ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

• [x] Yes
• [ ] No

Other information:

See discussions at https://github.com/vuejs/vue-loader/issues/1435

What kind of change does this PR introduce? (check at least one)

• [x] Bugfix
• [ ] Feature
• [ ] Code style update
• [ ] Refactor
• [ ] Docs
• [ ] Underlying tools
• [ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

• [ ] Yes
• [x] No

Other information:

Version

5.0.0-beta.2

Environment info

  System:
    OS: macOS 10.15.7
    CPU: (6) x64 Intel(R) Core(TM) i5-8500B CPU @ 3.00GHz
  Binaries:
    Node: 12.16.3 - /usr/local/bin/node
    Yarn: 1.17.3 - ~/.npm-global/bin/yarn
    npm: 6.14.8 - ~/.npm-global/bin/npm
  Browsers:
    Chrome: 92.0.4515.93
    Edge: Not Found
    Firefox: 90.0
    Safari: 14.1
  npmPackages:
    @vue/babel-helper-vue-jsx-merge-props:  1.2.1 
    @vue/babel-helper-vue-transform-on:  1.0.2 
    @vue/babel-plugin-jsx:  1.0.6 
    @vue/babel-plugin-transform-vue-jsx:  1.2.1 
    @vue/babel-preset-app:  5.0.0-beta.2 
    @vue/babel-preset-jsx:  1.2.4 
    @vue/babel-sugar-composition-api-inject-h:  1.2.1 
    @vue/babel-sugar-composition-api-render-instance:  1.2.4 
    @vue/babel-sugar-functional-vue:  1.2.2 
    @vue/babel-sugar-inject-h:  1.2.2 
    @vue/babel-sugar-v-model:  1.2.3 
    @vue/babel-sugar-v-on:  1.2.3 
    @vue/cli-overlay:  5.0.0-beta.2 
    @vue/cli-plugin-babel: ~5.0.0-beta.2 => 5.0.0-beta.2 
    @vue/cli-plugin-eslint: ^5.0.0-beta.2 => 5.0.0-beta.2 
    @vue/cli-plugin-router: ^5.0.0-beta.2 => 5.0.0-beta.2 
    @vue/cli-plugin-vuex: ^5.0.0-beta.2 => 5.0.0-beta.2 
    @vue/cli-service: ~5.0.0-beta.2 => 5.0.0-beta.2 
    @vue/cli-shared-utils:  5.0.0-beta.2 
    @vue/compiler-core:  3.1.5 
    @vue/compiler-dom:  3.1.5 
    @vue/compiler-sfc:  3.1.5 
    @vue/compiler-ssr:  3.1.5 
    @vue/component-compiler-utils:  3.2.2 
    @vue/eslint-config-prettier: ^6.0.0 => 6.0.0 
    @vue/shared:  3.1.5 
    @vue/web-component-wrapper:  1.3.0 
    eslint-plugin-vue: ^7.14.0 => 7.14.0 
    vue: ^2.6.11 => 2.6.14 
    vue-cli-plugin-style-resources-loader: ~0.1.5 => 0.1.5 
    vue-eslint-parser:  7.9.0 
    vue-gettext: ^2.1.12 => 2.1.12 
    vue-hot-reload-api:  2.3.4 
    vue-loader:  16.3.1 (15.9.7)
    vue-router: ^3.2.0 => 3.5.2 
    vue-style-loader:  4.1.3 
    vue-template-compiler: ^2.6.14 => 2.6.14 
    vue-template-es2015-compiler:  1.9.1 
    vuex: ^3.4.0 => 3.6.2 
  npmGlobalPackages:
    @vue/cli: Not Found

Steps to reproduce

publicPath:
    process.env.NODE_ENV === 'production'
      ? 'http://localhost:8000/static/frontend'
      : '/static/frontend',

What is expected?

Script publicPath is the same and is correct

<script src="http://localhost:8000/static/frontend/js/safari-nomodule-fix.js" type="module"></script>

What is actually happening?

Script publicPath is wrong, 2nd slash after http is omitted

<script src="http:/localhost:8000/static/frontend/js/safari-nomodule-fix.js" type="module"></script>

Why? How to pass absolute url for production? (I have all static files hosted on CDN on another domain)

i use esmodule in vue.config.js

Version

5.0.0-beta.2

code

//package.json

  "type": "module"

//vue.config.js

import postcssAutoAdaptive from './postcss-auto-adaptive'

module.exports = {
  devServer: {
    disableHostCheck: true,
    host: '0.0.0.0',
    port: 9521,
    proxy: {
      // change xxx-api/login => mock/login
      // detail: https://cli.vuejs.org/config/#devserver-proxy
      [process.env.VUE_APP_BASE_API]: {
        // target: `http://172.16.6.83:8080/`,
        target: `http://172.16.160.68:8080/`,
        changeOrigin: true,
        pathRewrite: {
          ['^' + process.env.VUE_APP_BASE_API]: '/'
        }
      }
    }
  },
  css: {
    loaderOptions: {
      postcss: {
        postcssOptions: {
          plugins: [
            postcssAutoAdaptive()
          ]
        }
      }
    }
  },
  publicPath: '/',
  outputDir: 'dist',
  lintOnSave: false,
  runtimeCompiler: true
}

Reproduction link

https://none

Environment info

Environment Info:

  System:
    OS: Windows 10 10.0.19042
    CPU: (12) x64 AMD Ryzen 5 3600 6-Core Processor
  Binaries:
    Node: 14.16.0 - D:\devlang\nodejs\node.EXE
    Yarn: Not Found
    npm: 6.14.11 - D:\devlang\nodejs\npm.CMD
  Browsers:
    Chrome: Not Found
    Edge: Spartan (44.19041.423.0), Chromium (91.0.864.70)
  npmPackages:
    @antv/x6-vue-shape: ^1.1.6 => 1.2.4
    @vue/babel-helper-vue-jsx-merge-props:  1.2.1
    @vue/babel-helper-vue-transform-on:  1.0.2
    @vue/babel-plugin-jsx:  1.0.6
    @vue/babel-plugin-transform-vue-jsx:  1.2.1
    @vue/babel-preset-app:  5.0.0-beta.2
    @vue/babel-preset-jsx:  1.2.4
    @vue/babel-sugar-composition-api-inject-h:  1.2.1
    @vue/babel-sugar-composition-api-render-instance:  1.2.4
    @vue/babel-sugar-functional-vue:  1.2.2
    @vue/babel-sugar-inject-h:  1.2.2
    @vue/babel-sugar-v-model:  1.2.3
    @vue/babel-sugar-v-on:  1.2.3
    @vue/cli-overlay:  5.0.0-beta.2
    @vue/cli-plugin-babel: ~5.0.0-beta.2 => 5.0.0-beta.2
    @vue/cli-plugin-eslint: ~5.0.0-beta.2 => 5.0.0-beta.2
    @vue/cli-plugin-router: ~5.0.0-beta.2 => 5.0.0-beta.2
    @vue/cli-plugin-typescript: ~5.0.0-beta.2 => 5.0.0-beta.2
    @vue/cli-plugin-vuex: ~5.0.0-beta.2 => 5.0.0-beta.2
    @vue/cli-service: ~5.0.0-beta.2 => 5.0.0-beta.2
    @vue/cli-shared-utils:  5.0.0-beta.2
    @vue/component-compiler-utils:  3.2.2
    @vue/composition-api: ^1.0.0-rc.10 => 1.0.0-rc.10
    @vue/eslint-config-typescript: ^7.0.0 => 7.0.0
    @vue/web-component-wrapper:  1.3.0
    babel-helper-vue-jsx-merge-props:  2.0.3
    eslint-plugin-vue: ^6.2.2 => 6.2.2
    typescript: ^4.2.4 => 4.3.5
    vue: ^2.6.14 => 2.6.14
    vue-axios: ^2.1.5 => 2.1.5
    vue-class-component: ^7.2.3 => 7.2.6
    vue-clipboard2: ^0.3.1 => 0.3.1
    vue-demi:  0.7.5
    vue-eslint-parser:  7.6.0
    vue-hot-reload-api:  2.3.4
    vue-loader:  16.3.1 (15.9.7)
    vue-property-decorator: ^9.1.2 => 9.1.2
    vue-router: ^3.2.0 => 3.5.1
    vue-style-loader:  4.1.3
    vue-template-compiler: ^2.6.14 => 2.6.14
    vue-template-es2015-compiler:  1.9.1
    vuex: ^3.6.2 => 3.6.2
    vuex-class: ^0.3.2 => 0.3.2
    vuex-class-modules: ^1.3.0 => 1.3.0
  npmGlobalPackages:
    @vue/cli: Not Found

Steps to reproduce

none

What is expected?

none

What is actually happening?

ERROR Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only file and data URLs are supported by the default ESM loader. On Windows, absolute paths must be valid file:// U RLs. Received protocol 'd:' Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only file and data URLs are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Rec eived protocol 'd:' at Loader.defaultResolve [as _resolve] (internal/modules/esm/resolve.js:782:11) at Loader.resolve (internal/modules/esm/loader.js:86:40) at Loader.getModuleJob (internal/modules/esm/loader.js:230:28) at Loader.import (internal/modules/esm/loader.js:165:28) at importModuleDynamically (internal/modules/cjs/loader.js:1006:27) at exports.importModuleDynamicallyCallback (internal/process/esm_loader.js:30:14) at loadFileConfig (D:\project\yoyosys\console\console-2.0-installer\console-install-ui\[email protected]\cli-service\lib\util\loadFileConfig.js:28:7) at Service.loadUserOptions (D:\project\yoyosys\console\console-2.0-installer\console-install-ui\[email protected]\cli-service\lib\Service.js:337:44) at Service.init (D:\project\yoyosys\console\console-2.0-installer\console-install-ui\[email protected]\cli-service\lib\Service.js:76:30) at Service.run (D:\project\yoyosys\console\console-2.0-installer\console-install-ui\[email protected]\cli-service\lib\Service.js:245:16) npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! [email protected] serve: vue-cli-service serve npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the [email protected] serve 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! C:\Users\Admin\AppData\Roaming\npm-cache_logs\2021-07-19T10_27_48_845Z-debug.log

Process finished with exit code 1

none

According to the contribution guidelines, I added the instructions on how to deploy a vue app to Stormkit to the master and the next branch. I tried to find the best place alphabetically, which is quiet difficult. How does this look to you?

What kind of change does this PR introduce? (check at least one)

• [ ] Bugfix
• [ ] Feature
• [ ] Code style update
• [ ] Refactor
• [x] Docs
• [ ] Underlying tools
• [ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

• [ ] Yes
• [x] No

Other information:

Version

4.5.13

Environment info

System:
  OS: Windows 10 10.0.19042
  CPU: (4) x64 Intel(R) Core(TM) i5-3570 CPU @ 3.40GHz   
Binaries:
  Node: 14.16.0 - C:\Program Files\nodejs\node.EXE       
  Yarn: Not Found
  npm: 6.14.8 - C:\Program Files\nodejs\npm.CMD
Browsers:
  Chrome: 91.0.4472.124
  Edge: Spartan (44.19041.1023.0), Chromium (91.0.864.67)
npmGlobalPackages:
  @vue/cli: Not Found

Steps to reproduce

• Run vue create foo -d && cd foo
• Run vue add pwa
• Now we have an unused public/img/icons/mstile-150x150.png image.

What is expected?

From my perspective, the public/img/icons directory should not contain any unused images.

What is actually happening?

The mstile-150x150.png file appears in the public/img/icons directory. However, I couldn't find any references to this image either in the source code or in a production build:

• No references in the <head> element.
• No references in the browserconfig.xml file (since it is not generated at all).
• No references in the manifest.json file.

Probably I missed something, and this file is used somewhere in the code. However, my current impression is that the mstile-150x150.png file is not needed in this repo (at least without browserconfig.xml).

Version

4.5.3

Environment info

Environment Info:

  System:
    OS: macOS 11.4
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
  Binaries:
    Node: 14.17.1 - /usr/local/bin/node
    Yarn: 1.22.10 - /usr/local/bin/yarn
    npm: 6.14.13 - /usr/local/bin/npm
  Browsers:
    Chrome: 91.0.4472.114
    Edge: Not Found
    Firefox: Not Found
    Safari: 14.1.1
  npmGlobalPackages:
    @vue/cli: 4.5.13

Steps to reproduce

In a terminal window, enter: vue create foo Continue until E2E preferences menu

What is expected?

Cypress appear in the menu as: Cypress

What is actually happening?

Cypress appears in the menu as: Cypress (Chrome only)

Cypress supports Firefox & Edge (since Cypress v4.0) Source: Cypress Official Blog