profile
viewpoint

Akryum/guijs 747

🐣️ The app that makes your #devlife easier.

sodatea/front-end-interview-questions-and-answers 10

Interview Questions & Answers

sodatea/cc98-ionic 4

A third-party client app for http://www.cc98.org/, powered by ionic framework

sodatea/friendly-errors-webpack-plugin 4

Recognizes certain classes of webpack errors and cleans, aggregates and prioritizes them to provide a better Developer Experience.

sodatea/hexo-theme-sleepless 4

A fork of the "apollo" hexo theme by pinggod

sodatea/blog 3

Hexo source for my personal blog: https://sodatea.github.io

sodatea/cc98-userscripts 3

userscripts for cc98

sodatea/fe-dotfiles 3

A collection of front-end project configurations

sodatea/get-current-script 3

get current executing script, with support for IE9+ and Firefox

sodatea/eslint-config-soda 2

ESLint configurations for my personal projects

issue commentvueComponent/jsx

error when use this package with vue 3 and vue router next

Or,

module.exports = {
  presets: [["@vue/cli-plugin-babel/preset", { jsx: false }]],
  plugins: ["@ant-design-vue/babel-plugin-jsx"]
};

nour-dev

comment created time in 6 hours

startedvueComponent/jsx

started time in a day

issue commentvuejs/vue-cli

High Security Vulnerability (Denial of Service) issue 1486 in http-proxy

@sailfish009 webpack-dev-server hasn't fixed this issue (see the link above). They've pinned the http-proxy version.

itsalaidbacklife

comment created time in a day

pull request commentvuejs/vuepress

fix($core): watch file changes event (fix #2392)

With this fix, the dev configuration is reloaded and the page refreshes, but somehow the new build still does not take the changed file into account.

Ideally, the configuration does not need to be reloaded, only a webpack rebuild needs to be triggered and the page should be hot updated by webpack, not by vuepress.

newsbielt703

comment created time in a day

issue closedvuejs/vue-cli

build as library error,This dependency was not found:* ~entry in ./node_modules/@vue/cli-service/lib/commands/build/entry-lib-no-default.js

Version

4.4.1

Reproduction link

https://github.com/zhouhuan327/awesome-wheels

Environment info

Environment Info:

  System:
    OS: Windows 10 10.0.18363
    CPU: (8) x64 Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
  Binaries:
    Node: 12.16.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.0 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
    npm: 6.13.4 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: 44.18362.449.0
  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.3 (4.4.1)
    @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.4.1
    @vue/cli-plugin-babel: ~4.2.0 => 4.2.3
    @vue/cli-plugin-router:  4.4.1
    @vue/cli-plugin-unit-jest: ~4.3.0 => 4.3.1
    @vue/cli-plugin-vuex:  4.4.1
    @vue/cli-service: ^4.4.1 => 4.4.1
    @vue/cli-shared-utils:  4.4.1 (4.2.3, 4.3.1)
    @vue/component-compiler-utils:  3.1.2 (3.1.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
    jest-serializer-vue:  2.0.2
    vue: ^2.6.11 => 2.6.11
    vue-hot-reload-api:  2.3.4
    vue-jest:  undefined (3.0.5)
    vue-loader:  15.9.2
    vue-router:  3.3.1
    vue-server-renderer:  2.6.11
    vue-style-loader:  4.1.2
    vue-template-compiler: ^2.6.11 => 2.6.11
    vue-template-es2015-compiler:  1.9.1
    vuepress: ^1.5.0 => 1.5.0
    vuepress-html-webpack-plugin:  undefined (3.2.0)
    vuepress-plugin-container:  2.1.4
    vuepress-plugin-smooth-scroll:  0.0.3
  npmGlobalPackages:
    @vue/cli: Not Found

Steps to reproduce

run vue-cli-service build --target lib --name myLibName src/index.js

What is expected?

build success

What is actually happening?

i got error tips three times

 ERROR  Failed to compile with 1 errors                                                                                                 4:47:43 PM

This dependency was not found:

* ~entry in ./node_modules/@vue/cli-service/lib/commands/build/entry-lib-no-default.js

To install it, you can run: npm install --save ~entry

run " vue-cli-service build" was successful but build with "target lib" can not

<!-- generated by vue-issues. DO NOT REMOVE -->

closed time in 2 days

zhouhuan327

issue commentvuejs/vue-cli

build as library error,This dependency was not found:* ~entry in ./node_modules/@vue/cli-service/lib/commands/build/entry-lib-no-default.js

Delete these lines: https://github.com/zhouhuan327/awesome-wheels/blob/2ae067c1245ebbb6f86b7d09777718898f8efafd/vue.config.js#L16-L27

These are all configured by default, and by calling Object.assign, you are overriding the default configuration fields such as the additional aliases required for the lib target.

(And upgrade @vue/cli-plugin-babel to ~4.4.0, seems there's a bug with the old version)

zhouhuan327

comment created time in 2 days

issue commentvuejs/vue-cli

vue ui: Invariant Violation

What about deleting the ~/.vue-cli-ui folder and then restarting the UI?

I have no idea why this happens and can't reproduce it by myself.

artnova-david

comment created time in 2 days

issue commentvuejs/vue-cli

Transpilation of @babel/runtime

Still waiting for this issue to be resolved https://github.com/babel/babel/issues/9277

micopiira

comment created time in 2 days

push eventvuejs/vue-cli

Lucas Werkmeister

commit sha 0809fc8a9c5dc23d44c598d5138d756cac4bc0c5

feat(babel-preset-app): pass full config to @babel/preset-env (#5522) Pass not just the useBuiltIns and corejs options, but the whole envOptions object, into the @babel/preset-env preset that is used to transform @babel/runtime, just like for the @babel/preset-env that is used for the application source code. This allows users to also specify other options, such as `exclude` and `polyfills`, and have them apply here too. In particular, this can be used to exclude the Promise polyfill, e. g. if Promise is already polyfilled in some other way. Previously, exclude: ['es.promise'], polyfills: ['es.array.iterator', 'es.object.assign'], could be used to configure the preset for the application source code, but the babel runtime would be transformed without those options, and so es.promise would still end up being included. Closes #5208

view details

push time in 2 days

PR merged vuejs/vue-cli

feat(babel-preset-app): pass full config to @babel/preset-env PR: Internal

Pass not just the useBuiltIns and corejs options, but the whole envOptions object, into the @babel/preset-env preset that is used to transform @babel/runtime, just like for the @babel/preset-env that is used for the application source code. This allows users to also specify other options, such as exclude and polyfills, and have them apply here too.

In particular, this can be used to exclude the Promise polyfill, e. g. if Promise is already polyfilled in some other way. Previously,

exclude: ['es.promise'],
polyfills: ['es.array.iterator', 'es.object.assign'],

could be used to configure the preset for the application source code, but the babel runtime would be transformed without those options, and so es.promise would still end up being included.

Closes #5208

<!-- Please don't delete this template -->

<!-- PULL REQUEST TEMPLATE --> <!-- (Update "[ ]" to "[x]" to check a box) -->

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

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

<!-- Note: When submitting documentation PRs, please target the master branch (https://cli.vuejs.org) or next branch (https://next.cli.vuejs.org) When submitting coding PRs, please target the dev branch. -->

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

  • [ ] Yes
  • [x] No (I think)

Other information:

+16 -4

6 comments

2 changed files

lucaswerkmeister

pr closed time in 2 days

issue closedvuejs/vue-cli

@vue/babel-preset-app option exclude conflict

Version

3.12.1

Reproduction link

https://github.com/vuejs/vue-cli/blob/dev/packages/%40vue/babel-preset-app/index.js#L8

Environment info

Chrome: 82

Steps to reproduce

at babel.config.js config exclude:['es6.promise']

What is expected?

build dist code exclude core-js es6.promise

What is actually happening?

only set exclude:['es6.promise'] then build dist code still include core-js es6.promise


require config polyfills:['es6.array.iterator','es6.object.assign'] rewrite defaultPolyfills

but node_modules/@babel/preset-env/lib/built-in-definitions.js has Promise definitions

const definitions = {
  builtins: {
    //...
    Map: ["es6.map"].concat(CommonIterators),
    Number: "es6.number.constructor",
    Promise: ["es6.object.to-string", "es6.promise"]
    //...
  }
}

may be defaultPolyfills can remove es6.promise

<!-- generated by vue-issues. DO NOT REMOVE -->

closed time in 2 days

ac88

pull request commentvuejs/vue-cli

feat(babel-preset-app): pass full config to @babel/preset-env

After investigation, there's still one edge case: https://github.com/babel/babel/issues/9277

So I think I'll go for this PR instead of removing transpilation at the moment.

lucaswerkmeister

comment created time in 2 days

pull request commentvuejs/vue-cli

feat(babel-preset-app): pass full config to @babel/preset-env

Thanks! Actually I was thinking about dropping the transpilation of @babel/runtime entirely considering https://github.com/babel/babel/issues/7597 has been fixed.

But I'm not sure if that's safe to do… Maybe this PR is a better option before the runtime is sure to be bug-free.

lucaswerkmeister

comment created time in 2 days

Pull request review commentvuejs/vue-cli

Allow integrity hashes for prefetch links

 module.exports = class CorsPlugin {               if (hash) {                 tag.attributes.integrity = hash               }-            } else if (tag.tagName === 'link' && tag.attributes.rel === 'stylesheet') {+            } else if (tag.tagName === 'link' && (tag.attributes.rel === 'stylesheet' || tag.attributes.rel === 'prefetch')) {

If I'm not mistaken, the linked issue only said it's implemented for preload links, not prefetch.

And Line#49-56 needs to be removed too.

chaitanyapotti

comment created time in 2 days

push eventvuejs/vue-cli

Saleh Alghusson

commit sha 22c8a22dacfe9127460bcccda2d17da18dc4af3a

docs: mention using `null` to ignore icons (#5530)

view details

push time in 2 days

PR merged vuejs/vue-cli

Update README.md PR: Documentation

<!-- Please don't delete this template -->

<!-- PULL REQUEST TEMPLATE --> <!-- (Update "[ ]" to "[x]" to check a box) -->

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:

<!-- Note: When submitting documentation PRs, please target the master branch (https://cli.vuejs.org) or next branch (https://next.cli.vuejs.org) When submitting coding PRs, please target the dev branch. -->

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

  • [ ] Yes
  • [x] No

Other information: This change was introduced in v4.3.0 but the docs were not updated. Here is the pr where it got included #5087.

+1 -1

0 comment

1 changed file

qirh

pr closed time in 2 days

PR closed vuejs/vue-cli

fix(msg prop text): update text to match cypress typescript spec

<!-- Please don't delete this template -->

<!-- PULL REQUEST TEMPLATE --> <!-- (Update "[ ]" to "[x]" to check a box) -->

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:

<!-- Note: When submitting documentation PRs, please target the master branch (https://cli.vuejs.org) or next branch (https://next.cli.vuejs.org) When submitting coding PRs, please target the dev branch. -->

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

  • [ ] Yes
  • [x] No

Other information:

+1 -1

1 comment

1 changed file

Nickrosendo

pr closed time in 2 days

pull request commentvuejs/vue-cli

fix(msg prop text): update text to match cypress typescript spec

But that's not how it's supposed to be fixed. See https://cli.vuejs.org/dev-guide/plugin-dev.html#editing-existing-templates

- !!js/regexp /Welcome to Your Vue\.js App/ is the regexp to match the content in @vue/cli-plugin-router/generator/template/src/views/Home.vue.

I think the problem might reside somewhere else.

Nickrosendo

comment created time in 2 days

pull request commentvuejs/vuepress

fix(hmr): upgrade http-proxy

The bug is that chokidar used by vuepress and webpack resolves to different instances.

https://github.com/vuejs/vuepress/blob/c6a3cb59275b095bc69e392d77a982a6334f6551/packages/%40vuepress/core/lib/node/dev/index.js#L67-L79

I'd like to explain in detail but it's too late here, I need to go to bed now. So here's the short version:

The implementation in vuepress was never correct. It didn't listen to change events. It's just that when webpack and vuepress use the same chokidar instance, the listener in webpack also reacts to the source files' change events, so hot reload happens to work.

(Or, maybe it's intentional to reuse the same chokidar instance? But such usage is not reliable anyway. It should be fixed)

posva

comment created time in 3 days

pull request commentvuejs/vuepress

fix(hmr): upgrade http-proxy

  1. Upgrading yarn.lock in the project does not fix a bug in the userland.
  2. As described, a linked vuepress dependency fixed the problem. It's because the lockfile in this project hasn't been updated in months, it does not have the newly-introduced broken dependency anyway.

The root problem is chokidar - I'm still trying to understand why chokidar v3 in watchpack breaks the functionality, but the problem lies there.

posva

comment created time in 3 days

pull request commentvuejs/vuepress

fix(hmr): upgrade http-proxy

I don't think it fixed that problem.

posva

comment created time in 3 days

issue commentvuejs/vue-cli

vue cli fails to get packages when npm is using a custom nexus npm registry

Ah, right. Because Vue CLI used to call yarn info or npm info to get the package metadata underlyingly. Later it was refactored for performance concerns. (Starting a subprocess is very slow on Windows, and in the UI page for "dependencies" there might be tens of simultaneous calls to getMetadata)

Ealdst

comment created time in 3 days

issue commentvuejs/vue-cli

ESLint version check during @vue/cli-plugin-eslint upgrade

😅 Yeah that's really misleading. Thanks for reporting!

service-paradis

comment created time in 3 days

push eventsodatea/jsx-1

Haoqun Jiang

commit sha 4573b93187915711e33fabe15fe68f3fa59fb93b

chore: enable useWorkspaces in lerna

view details

push time in 3 days

PR opened vuejs/vue-test-utils

docs: replace BABEL_ENV with NODE_ENV

According to the babel documentation, NODE_ENV can also be recognized when loading configurations, and NODE_ENV has better interoperability in the ecosystem.

Here's a use case that NODE_ENV works well while BABEL_ENV might cause confusion: https://github.com/vuejs/vue-cli/issues/5525#issuecomment-634523493

<!-- Please make sure to read the Pull Request Guidelines: https://github.com/vuejs/vue-test-utils/blob/dev/.github/CONTRIBUTING.md#pull-request-guidelines -->

<!-- PULL REQUEST TEMPLATE --> <!-- (Update "[ ]" to "[x]" to check a box) -->

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

  • [ ] Bugfix
  • [ ] Feature
  • [ ] Code style update
  • [ ] Refactor
  • [ ] Build-related changes
  • [x] Other, please describe: Documentation

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

  • [ ] Yes
  • [x] No

If yes, please describe the impact and migration path for existing applications:

The PR fulfills these requirements:

  • [x] It's submitted to the dev branch.
  • [x] When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)
  • [x] All tests are passing: https://github.com/vuejs/vue-test-utils/blob/dev/.github/CONTRIBUTING.md#development-setup
  • [x] New/updated tests are included

If adding a new feature, the PR's description includes:

  • [ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

+4 -4

0 comment

1 changed file

pr created time in 3 days

create barnchsodatea/vue-test-utils

branch : doc-karma-node-env

created branch time in 3 days

fork sodatea/vue-test-utils

🔬 Utilities for testing Vue components

https://vue-test-utils.vuejs.org

fork in 3 days

push eventsodatea/jsx-1

Haoqun Jiang

commit sha 866ea462935e044e42d8c95c05d3d98ecbb7aa6c

chore: add missing peer dependency for `@vue/test-utils`

view details

push time in 3 days

PR opened vueComponent/jsx

chore: improve setup of the tooling

Cleaned up the configurations and incorporated common best practices in the ecosystem.

+10472 -59

0 comment

12 changed files

pr created time in 3 days

create barnchsodatea/jsx-1

branch : tooling

created branch time in 3 days

create barnchsodatea/jsx

branch : tooling

created branch time in 3 days

PR opened vuejs/vue-test-utils-next

chore: @vue/compiler-sfc is not a peer dependency

If I'm not mistaken, @vue/compiler-sfc is never used in this codebase. It seems to be a peer dependency of vue-jest v5 (but somehow not explicitly specified).

But as this library is framework agnostic, the peer dependency of vue-jest should not imply a peer dependency of the library. For users who don't need to test .vue files, @vue/compiler-sfc is extraneous.

+0 -1

0 comment

1 changed file

pr created time in 3 days

create barnchsodatea/vue-test-utils-next

branch : remove-compiler-sfc-peer-dep

created branch time in 3 days

issue closedvuejs/vue-cli

macOS 10.15.2 使用vue ui命令报错

Version

4.4.1

Environment info

System:
    OS: macOS 10.15.2
    CPU: (12) x64 Intel(R) Core(TM) i7-8850H CPU @ 2.60GHz
  Binaries:
    Node: 13.1.0 - /usr/local/bin/node
    Yarn: Not Found
    npm: 6.14.5 - /usr/local/bin/npm
  Browsers:
    Chrome: 83.0.4103.61
    Edge: Not Found
    Firefox: Not Found
    Safari: 13.0.4
  npmPackages:
    @vue/cli:  4.4.1
    @vue/cli-shared-utils:  4.4.1
    @vue/cli-ui:  4.4.1
    @vue/cli-ui-addon-webpack:  4.4.1
    @vue/cli-ui-addon-widgets:  4.4.1
    typescript:  3.9.3
    vue:  2.6.11
    vue-cli-plugin-apollo:  0.21.3
    vue-jscodeshift-adapter:  2.1.0
    vue-sfc-descriptor-to-string:  1.0.0
    vue-template-compiler:  2.6.11
  npmGlobalPackages:
    @vue/cli: 4.4.1

Steps to reproduce

vue ui

What is expected?

open vue ui window.

What is actually happening?

internal/modules/cjs/loader.js:548 throw e; ^

Error: Package exports for '/usr/local/lib/node_modules/@vue/cli/node_modules/apollo-engine-reporting/node_modules/uuid' do not define a valid '.' target at resolveExportsTarget (internal/modules/cjs/loader.js:545:13) at applyExports (internal/modules/cjs/loader.js:459:14) at resolveExports (internal/modules/cjs/loader.js:508:12) at Function.Module._findPath (internal/modules/cjs/loader.js:577:20) at Function.Module._resolveFilename (internal/modules/cjs/loader.js:879:27) at Function.Module._load (internal/modules/cjs/loader.js:785:27) at Module.require (internal/modules/cjs/loader.js:956:19) at require (internal/modules/cjs/helpers.js:74:18) at Object.<anonymous> (/usr/local/lib/node_modules/@vue/cli/node_modules/apollo-engine-reporting/dist/agent.js:26:16) at Module._compile (internal/modules/cjs/loader.js:1063:30) { code: 'MODULE_NOT_FOUND' }

<!-- generated by vue-issues. DO NOT REMOVE -->

closed time in 3 days

leapp

issue commentvuejs/vue-cli

macOS 10.15.2 使用vue ui命令报错

https://github.com/nodejs/modules/issues/446 Please upgrade your Node.js version.

leapp

comment created time in 3 days

fork sodatea/jsx-1

jsx for vue 3

fork in 3 days

startedJSCIG/es-discuss

started time in 4 days

issue closedvuejs/vue-cli

Environment Variables can be expand

What problem does this feature solve?

like dotenv expand

PORT=3000
VUE_APP_API_HOST=http://localhost:${PORT}

https://github.com/motdotla/dotenv-expand/blob/master/test/.env

What does the proposed API look like?

NODE_ENV=test BASIC=basic BASIC_EXPAND=$BASIC MACHINE=machine_env MACHINE_EXPAND=$MACHINE UNDEFINED_EXPAND=$UNDEFINED_ENV_KEY ESCAPED_EXPAND=$ESCAPED MONGOLAB_DATABASE=heroku_db MONGOLAB_USER=username MONGOLAB_PASSWORD=password MONGOLAB_DOMAIN=abcd1234.mongolab.com MONGOLAB_PORT=12345 MONGOLAB_URI=mongodb://${MONGOLAB_USER}:${MONGOLAB_PASSWORD}@${MONGOLAB_DOMAIN}:${MONGOLAB_PORT}/${MONGOLAB_DATABASE}

MONGOLAB_USER_RECURSIVELY=${MONGOLAB_USER}:${MONGOLAB_PASSWORD} MONGOLAB_URI_RECURSIVELY=mongodb://${MONGOLAB_USER_RECURSIVELY}@${MONGOLAB_DOMAIN}:${MONGOLAB_PORT}/${MONGOLAB_DATABASE}

WITHOUT_CURLY_BRACES_URI=mongodb://$MONGOLAB_USER:$MONGOLAB_PASSWORD@$MONGOLAB_DOMAIN:$MONGOLAB_PORT/$MONGOLAB_DATABASE WITHOUT_CURLY_BRACES_USER_RECURSIVELY=$MONGOLAB_USER:$MONGOLAB_PASSWORD WITHOUT_CURLY_BRACES_URI_RECURSIVELY=mongodb://$MONGOLAB_USER_RECURSIVELY@$MONGOLAB_DOMAIN:$MONGOLAB_PORT/$MONGOLAB_DATABASE

<!-- generated by vue-issues. DO NOT REMOVE -->

closed time in 4 days

IndexXuan

issue commentvuejs/vue-cli

Error deploy vue with router to Heroku : This relative module was not found: * ./router in ./src/main.js

Oops, misunderstood the documentaion. Please ignore my previous advice.

Please check the core.excludesFile option in ~/.gitconfig

FabriceSALAH

comment created time in 4 days

issue commentvuejs/vue-cli

Error deploy vue with router to Heroku : This relative module was not found: * ./router in ./src/main.js

I have. But it works fine on my side. As the git documentation said, patterns in .gitignore files of any parent directory will also be respected (https://git-scm.com/docs/gitignore), could you also try to look at some of your upper-level directories for some clue?

FabriceSALAH

comment created time in 4 days

issue closedvuejs/vue-cli

Error installing with npm

Version

4.4.1

Environment info

Vue is not installed

Steps to reproduce

npm install -g @vue/cli

What is expected?

Vue cli should install globally to the latest version

What is actually happening?

It errors:

114 verbose stack SyntaxError: Unexpected end of JSON input while parsing near "...oi":"^14.3.0","launch'
114 verbose stack     at JSON.parse (<anonymous>)
114 verbose stack     at parseJson (C:\Program Files\nodejs\node_modules\npm\node_modules\json-parse-better-errors\index.js:7:17)
114 verbose stack     at C:\Program Files\nodejs\node_modules\npm\node_modules\node-fetch-npm\src\body.js:96:50
114 verbose stack     at processTicksAndRejections (internal/process/task_queues.js:97:5)

<!-- generated by vue-issues. DO NOT REMOVE -->

closed time in 4 days

Ethilios

issue commentvuejs/vue-cli

Error installing with npm

Likely a network/cache issue. Please run npm cache verify and then try again. If that doesn't work, run npm cache clean -f and try again.

Ethilios

comment created time in 4 days

PR opened vuejs/vue-cli

fix(nightwatch): should not install corresponding webdriver if the browser is unselected PR: Bug Fix

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:

<!-- Note: When submitting documentation PRs, please target the master branch (https://cli.vuejs.org) or next branch (https://next.cli.vuejs.org) When submitting coding PRs, please target the dev branch. -->

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

  • [ ] Yes
  • [x] No

Other information:

+17 -14

0 comment

1 changed file

pr created time in 4 days

create barnchsodatea/vue-cli

branch : fix-unselect-firefox

created branch time in 4 days

push eventsodatea/vue-cli

Haoqun Jiang

commit sha 8bcfea27928c240ff51fd7cf53ac099a2f315029

ci: remove extraneous v

view details

push time in 4 days

push eventsodatea/vue-cli

Haoqun Jiang

commit sha b66c6e200dce5000a8c29f0634a698c219a4aa54

ci: add minor version

view details

push time in 4 days

push eventsodatea/vue-cli

Haoqun Jiang

commit sha 2e75754eb0135b4ab7b2d9203167d820a3a1636e

ci: minimum setup

view details

push time in 4 days

create barnchsodatea/vue-cli

branch : ci-matrix

created branch time in 4 days

issue closedvuejs/vue-cli

set development browserslist to modern browsers in package.json to simplify debug

What problem does this feature solve?

I'm beginner javascript / vue developer.

Out of box debug experience with default vue cli project is not perfect. When trying to debug application, it was really hard to use console / inspect application state.

After setup it is much easier to debug.

What does the proposed API look like?

in default package.json:

"browserslist": [
      "> 1%",
      "last 2 versions",
      "not ie <= 8"
    ]
  }

change to:

"browserslist": {
    "production": [
      "> 1%",
      "last 2 versions",
      "not ie <= 8"
    ],
    "development": [
      "last 1 chrome version",
      "last 1 firefox version"
    ]
  }

<!-- generated by vue-issues. DO NOT REMOVE -->

closed time in 4 days

jarek102

issue commentvuejs/vue-cli

set development browserslist to modern browsers in package.json to simplify debug

Thanks for the advice. But for debugging, we've already had source map enabled. So I don't think it's necessary, and it may confuse some people if they want to visit the dev server on IE.

jarek102

comment created time in 4 days

issue closedvuejs/vue-cli

多页面打包assets资源路径引用错误

Version

3.5.5

Environment info

Environment Info:

  System:
    OS: macOS 10.14.4
    CPU: (4) x64 Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz
  Binaries:
    Node: 11.12.0 - /usr/local/bin/node
    Yarn: Not Found
    npm: 6.7.0 - /usr/local/bin/npm
  Browsers:
    Chrome: 73.0.3683.86
    Firefox: Not Found
    Safari: 12.1
  npmGlobalPackages:
    @vue/cli: 3.5.4

Steps to reproduce

这是我的vue.config.js配置

module.exports = {
    publicPath: "./",
    assetsDir: "./static",
    pages: {
        // 首页
        index: {
            entry: "src/pages/index/main.js",
            template: "public/index.html",
            title: "物流知识库"
        },
        // 专题
        column_index: {
            entry: "src/pages/column/index/main.js",
            filename: "./special/index.html",
            title: "专题"
        }
    }
};

我在专题页面指定了filename 路径,打包后生成的页面无法正确引用 `

module.exports = {
    publicPath: "./",
    assetsDir: "./static",
    pages: {
        // 首页
        index: {
            entry: "src/pages/index/main.js",
            template: "public/index.html",
            title: "物流知识库"
        },
        // 专题
        column_index: {
            entry: "src/pages/column/index/main.js",
            filename: "./special/index.html",
            title: "专题"
        }
    }
};

我在专题页面指定了filename 路径,打包后生成的页面无法正确引用 static目录下的静态资源,请问能在multi-page 模式下多一个字段自定义引用的资源路径吗

What is expected?

多页面可自定义静态资源路径

What is actually happening?

多页面目前不可自定义静态资源路径

<!-- generated by vue-issues. DO NOT REMOVE -->

closed time in 4 days

Leslie-Luo

issue closedvuejs/vue-cli

Option to not install vue as a dependency

What problem does this feature solve?

I really like vue-cli for its ease of use while still being highly customizable. My team has integrated vue-cli smoothly into our workflow using a custom plugin. This process is working so great that we have started experimenting with using it for non-Vue projects as well. However, since Vue is always automatically installed as a dependency, we have to remove it manually after install, which is time-consuming.

In short, we would like a command-line option to not automatically install vue, to be able to use vue-cli for non-vue projects.

What does the proposed API look like?

vue create would get a new option that could be called --no-vue. If present, cli-service generator would skip adding vue and vue-template-compiler as dependencies.

I am willing to help implement this feature if it is found to be within the scope of this project.

<!-- generated by vue-issues. DO NOT REMOVE -->

closed time in 4 days

petterw03

issue closedvuejs/vue-cli

Upgrade dependencies to core-js@3

Version

4.2.3

Environment info

  System:
    OS: Windows Server 2016 10.0.14393
    CPU: (4) x64 Intel(R) Xeon(R) CPU E5-2680 v4 @ 2.40GHz
  Binaries:
    Node: 13.9.0 - C:\Program Files\nodejs\node.EXE
    Yarn: Not Found
    npm: 6.13.7 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Not Found
  npmGlobalPackages:
    @vue/cli: Not Found

Steps to reproduce

C:> npm i -g @vue/cli

npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142 npm WARN deprecated core-js@2.6.11: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.

What is expected?

Installation of the vue/cli without error messages or deprecation warnings.

What is actually happening?

Deprecation warnings pop up about packages that are no longer safe to use.

<!-- generated by vue-issues. DO NOT REMOVE -->

closed time in 4 days

DarkLite1

issue commentvuejs/vue-cli

Upgrade dependencies to core-js@3

The core-js one should have been fixed with the latest release of apollo. The request one is tracked at https://github.com/vuejs/vue-cli/issues/5220

DarkLite1

comment created time in 4 days

issue closedvuejs/vue-cli

Install tailwind causing compiler to stop

Version

4.2.2

Reproduction link

https://github.com/minhchu/vue-tailwind-test

Check src/views/About.vue

Environment info

System:
    OS: Linux 4.15 Ubuntu 16.04.6 LTS (Xenial Xerus)
    CPU: (4) x64 Intel(R) Core(TM) i3-8100 CPU @ 3.60GHz
  Binaries:
    Node: 12.15.0 - ~/.nvm/versions/node/v12.15.0/bin/node
    Yarn: 1.21.1 - ~/.yarn/bin/yarn
    npm: 6.13.4 - ~/.nvm/versions/node/v12.15.0/bin/npm
  Browsers:
    Chrome: 79.0.3945.130
    Firefox: 72.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.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/preload-webpack-plugin:  1.1.1
    @vue/web-component-wrapper:  1.2.0
    eslint-plugin-vue: ^6.1.2 => 6.1.2
    vue: ^2.6.11 => 2.6.11
    vue-cli-plugin-tailwind: ~1.2.0 => 1.2.0
    vue-eslint-parser:  7.0.0
    vue-hot-reload-api:  2.3.4
    vue-loader:  15.8.3
    vue-router: ^3.1.5 => 3.1.5
    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: Not Found

Steps to reproduce

yarn install yarn run serve

What is expected?

App is compiled

What is actually happening?

It is not compiled

Screenshot from 2020-02-10 12-08-56


I don't know whether this bug come from vue-cli or vue-cli-plugin-tailwind

<!-- generated by vue-issues. DO NOT REMOVE -->

closed time in 4 days

minhchu

issue commentvuejs/vue-cli

Install tailwind causing compiler to stop

The culprit is prettier actually. It has a serious performance issue with deeply nested tags (https://github.com/prettier/prettier/issues/4672) - which is the case of the SVG element here: https://github.com/minhchu/vue-tailwind-test/blob/7118d094a17e700c7048f5aee15b25b1f5b34d71/src/views/About.vue#L32

Solution:

  1. Add a <!-- prettier-ignore --> comment before the SVG tag
  2. Or, as the issue has been fixed in prettier v2, you can run yarn add -D prettier@2 to upgrade it to the latest version
minhchu

comment created time in 4 days

issue closedvuejs/vue-cli

vue cli4 cannot be configured according to karma, but cli3 can succeed

Version

4.1.2

Reproduction link

https://github.com/heyi-let/vue-cli4_unit_karma

Environment info

System: OS: macOS Mojave 10.14.5 CPU: (8) x64 Intel(R) Core(TM) i5-8259U CPU @ 2.30GHz Binaries: Node: 11.14.0 - ~/.nvm/versions/node/v11.14.0/bin/node Yarn: Not Found npm: 6.7.0 - ~/.nvm/versions/node/v11.14.0/bin/npm Browsers: Chrome: 81.0.4044.138 Firefox: 71.0 Safari: 12.1.1 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.4.1 @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.4.1 @vue/cli-plugin-babel: ^4.4.0 => 4.4.1 @vue/cli-plugin-e2e-cypress: ^4.4.0 => 4.4.1 @vue/cli-plugin-eslint: ^4.4.0 => 4.4.1 @vue/cli-plugin-router: ^4.4.0 => 4.4.1 @vue/cli-plugin-unit-mocha: ^4.4.0 => 4.4.1 @vue/cli-plugin-vuex: ^4.4.0 => 4.4.1 @vue/cli-service: ^4.4.0 => 4.4.1 @vue/cli-shared-utils: 4.4.1 @vue/component-compiler-utils: 3.1.2 @vue/eslint-config-standard: ^5.1.2 => 5.1.2 @vue/preload-webpack-plugin: 1.1.1 @vue/test-utils: ^1.0.3 => 1.0.3 @vue/web-component-wrapper: 1.2.0 eslint-plugin-vue: ^6.2.2 => 6.2.2 vue: ^2.6.11 => 2.6.11 vue-eslint-parser: 7.1.0 vue-hot-reload-api: 2.3.4 vue-loader: 15.9.2 vue-router: ^3.2.0 => 3.2.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.4.0 => 3.4.0 npmGlobalPackages: @vue/cli: 4.1.2

Steps to reproduce

git clone https://github.com/heyi-let/vue-cli4_unit_karma

The test:unit can be executed successfully in the cli-service4 branch.

git checkout cli-service3

npm install

npm run test:unit

But will fail in the cli-service4 branch

git checkout cli-service4

npm install

npm run test:unit

They have different @vue/cli-service versions,everything else is the same.

What is expected?

Can successfully run when using cli4

What is actually happening?

failed

<!-- generated by vue-issues. DO NOT REMOVE -->

closed time in 4 days

heyi-let

issue commentvuejs/vue-cli

vue cli4 cannot be configured according to karma, but cli3 can succeed

Please add a NODE_ENV=test prefix to the test command.


The reason: https://github.com/vuejs/vue-cli/commit/dfe3987d9f4208a3b4cf4bcf0315aa7887148a7e

Karma can't handle split chunks.

  • In @vue/cli-service v3, unless you explicitly set NODE_ENV to production, splitChunks won't be turned on.
  • In @vue/cli-service v4, unless you explicitly set NODE_ENV to test, splitChunks will be turned on by default.

It is a good practice to always set NODE_ENV to test during unit testing because many of the packages in Node.js ecosystem follows this convention.

Actually, with NODE_ENV=test, you can skip BABEL_ENV=test because it will default to NODE_ENV.

heyi-let

comment created time in 4 days

issue closedvuejs/vue-cli

css相关loader如何处理node_modules下面的导入的样式呢

What problem does this feature solve?

我的node_modules是通过npm link安装的。这个时候会出现以下问题。babel还未验证是否有问题

我想让postcss的autoprefixer插件去处理node_modules下面导入的特定文件,但是我写了如下配置无效: chainWebpack: config => { config.module .rule('postcss') .test(/\.css$/) .include .add(/node_modules\/custom-module\//) .end() .use('postcss-loader') .loader('postcss-loader') .options({ plugins: { autoprefixer: {} } }) }, 我希望导入这个模块下面的样式文件时,能被postcss处理,自动添加前缀, 代码: 在main.js:import 'custom-module/style/xxx.css' ;实际上还是原来的内容,并没有添加前缀

What does the proposed API look like?

就像transpileDependencies这个属性可以让babel处理一样,希望对css也有效

<!-- generated by vue-issues. DO NOT REMOVE -->

closed time in 4 days

kagari2613

issue commentvuejs/vue-cli

css相关loader如何处理node_modules下面的导入的样式呢

Closing due to inactivity

kagari2613

comment created time in 4 days

push eventvuejs/vue-cli

Haoqun Jiang

commit sha 611d869097ca5b4e9e2241644fe58b00fa3c20ad

test: bump test timeout seems appveyor tests are too slow to execute

view details

Domenico Gemoli

commit sha 6b68a4153c2edf6df9c0b2b6bfa769e0e01116f9

fix(nightwatch): fix `globals.js` import in config (#5387) closes #5171

view details

Haoqun Jiang

commit sha 9d481759f9b18148046bf15ed8391958e4c67a4c

test: force click 'finish-install' as there seems to be a bug in cypress

view details

Haoqun Jiang

commit sha 320e3919c9000c5c00be21b30445393b7d4765cc

style: fix some lint warnings

view details

Stefano Bartoletti

commit sha 1afae5836fd31373b08b961df649faef8ff03b80

chore: add 'pnpm-debug.log' to '_gitignore' (#5429)

view details

Haoqun Jiang

commit sha 5ac62da4c294d017aaf1c345521052285a6ad4a2

chore: disable gql linting

view details

Haoqun Jiang

commit sha 8d1056268ea2c7769305ed9c3ba2fdd7ef527aba

chore: dependency maintenance

view details

Haoqun Jiang

commit sha 6e8ddcccd73d9000f7d35b3b64eb3f0025fffa9f

ci: disable thread-loader on circleci

view details

Drew Bragg

commit sha caa3006ea85f5637a04c6dd467fbe119348805a1

docs: explain pwa head/manifest icons (#5408)

view details

Jiang Guoxi

commit sha d405f23e72e9e9560c448e581361e6e000f2029c

fix: set timeout of openChrome.applescript (#5390)

view details

epixian

commit sha 3c286d670e48b7c757991a101e28c38ec6e0b268

refactor: remove superflous vertices from the svg file (#5416)

view details

Haoqun Jiang

commit sha 5e93d70e6552d71b1600b289a30f77946813089c

fix: normalize the `file` argument of `transformScript`, fix Windows compatibility (#5424)

view details

Adrian B. Danieli

commit sha c64afc3c2a8854aae30fbfb85e92c0bb8b07bad7

feat(cli-service): add stdin flag to build (#5376)

view details

Romain

commit sha e2f00d2867269b411c7b1a7c703b7222a6185d84

fix(ui): fix "update all plugins/dependencies" utility (#5395)

view details

杨昆

commit sha a91649e8c04a47b527515d2768809901a2f81c2f

fix(eslint): invalidate the cache when `.eslintignore` changes (#5455)

view details

Albert Brand

commit sha 96dfd581b6917c34f9be058afad26e112aac52ef

fix(serve): pass devServer sockPath properly to client (#4800) closes #4400 closes #4430

view details

Haoqun Jiang

commit sha 75c398f04e7cd7b318be3519f27f1bb0e69ebcae

fix(creator): do not override the README.md generated by plugins (#5472) closes #4802 closes #4942

view details

tommyo

commit sha 16d2701011e6e660850da5b4f1bed185bbcd0b3c

fix(mocha): avoid `--inspect-brk` flag clobbering other values (#5473)

view details

Haoqun Jiang

commit sha 90f114640c35edd19ad85b6b80c1f64193ce671f

fix(ui): the logs from creator should be displayed in the UI (#5493) With `logWithSpinner`, the log would be output to the console instead. Fixes #5240 Fixes #5445

view details

Haoqun Jiang

commit sha 8b01c9ec516850d236f250d692cae038f0e1c37f

chore: dependency maintenance (#5496)

view details

push time in 5 days

issue closedvuejs/vue-cli

Error deploy vue with router to Heroku : This relative module was not found: * ./router in ./src/main.js

When I create a Vue project with CLI with router : "vue create myProject"

The project works in local.

But I cannot deploy this project on Heroku

Version

4.3.1

Reproduction link

https://github.com/FabriceSALAH/20200526_issuesForVueCliService

Environment info

System:
    OS: macOS High Sierra 10.13.6
    CPU: (8) x64 Intel(R) Core(TM) i7-4750HQ CPU @ 2.00GHz
  Binaries:
    Node: 12.16.3 - ~/.nvm/versions/node/v12.16.3/bin/node
    Yarn: 1.17.3 - /usr/local/bin/yarn
    npm: 6.14.4 - ~/.nvm/versions/node/v12.16.3/bin/npm
  Browsers:
    Chrome: 81.0.4044.138
    Edge: Not Found
    Firefox: 69.0
    Safari: 13.1
  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.3.1 
    @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.3.1 
    @vue/cli-plugin-babel: ~4.3.0 => 4.3.1 
    @vue/cli-plugin-eslint: ~4.3.0 => 4.3.1 
    @vue/cli-plugin-router: ~4.3.0 => 4.3.1 
    @vue/cli-plugin-vuex:  4.3.1 
    @vue/cli-service: ~4.3.0 => 4.3.1 
    @vue/cli-shared-utils:  4.3.1 
    @vue/component-compiler-utils:  3.1.2 
    @vue/eslint-config-prettier: ^6.0.0 => 6.0.0 
    @vue/preload-webpack-plugin:  1.1.1 
    @vue/web-component-wrapper:  1.2.0 
    eslint-plugin-vue: ^6.2.2 => 6.2.2 
    vue: ^2.6.11 => 2.6.11 
    vue-eslint-parser:  7.1.0 
    vue-hot-reload-api:  2.3.4 
    vue-loader:  15.9.2 
    vue-router: ^3.1.6 => 3.2.0 
    vue-style-loader:  4.1.2 
    vue-template-compiler: ^2.6.11 => 2.6.11 
    vue-template-es2015-compiler:  1.9.1 
  npmGlobalPackages:
    @vue/cli: Not Found

Steps to reproduce

Create vue project with CLI with router and add this configuration : https://cli.vuejs.org/guide/deployment.html#heroku

What is expected?

to build and deploye with succes on heroku

What is actually happening?

remote: -----> Build remote: Running build remote:
remote: > test_vue_router_to_heroku@0.1.0 build /tmp/build_ba6426395db88aaa98be1e0cd8e8e70b remote: > vue-cli-service build remote:
remote:
remote: - Building for production... remote: ERROR Failed to compile with 1 errors4:10:21 PM remote:
remote: This relative module was not found: remote:
remote: * ./router in ./src/main.js remote: ERROR Build failed with errors. remote: npm ERR! code ELIFECYCLE remote: npm ERR! errno 1 remote: npm ERR! test_vue_router_to_heroku@0.1.0 build: vue-cli-service build remote: npm ERR! Exit status 1 remote: npm ERR! remote: npm ERR! Failed at the test_vue_router_to_heroku@0.1.0 build script. remote: npm ERR! This is probably not a problem with npm. There is likely additional logging output above. remote: remote: npm ERR! A complete log of this run can be found in: remote: npm ERR! /tmp/npmcache.vPL77/_logs/2020-05-26T16_10_21_473Z-debug.log remote: remote: -----> Build failed

<!-- generated by vue-issues. DO NOT REMOVE -->

closed time in 5 days

FabriceSALAH

issue commentvuejs/vue-cli

Error deploy vue with router to Heroku : This relative module was not found: * ./router in ./src/main.js

But it's not ignored by default - just have a look at the .gitignore file https://github.com/FabriceSALAH/20200526_issuesForVueCliService/blob/master/.gitignore

Maybe it's in your ~/.gitignore_global?

FabriceSALAH

comment created time in 5 days

issue commentvuejs/vue-cli

Improve --skip-plugins

Sorry for the late reply.

It's because it's not the design goal of this flag - if you take a look at the original PR, it says this option is to "skip (plugins) for this run", meaning it's a one-off command that doesn't affect the original plugin loading logic.

Anyway, I feel it's okay to skip the plugin loading at all. Though, it's a low-priority for us to implement, given the abovementioned alternative workarounds. You are welcome to open a PR to address this issue and we'll be glad to accept it, but we are not likely to implement it on our own in the foreseeable future.

Fl0pZz

comment created time in 5 days

issue commentvuejs/vue-cli

vue cli4 cannot be configured according to karma, but cli3 can succeed

Thanks for submitting this issue. Due to our limited time, we have to ask you to include a reproduction link to a minimal full reproduction of your problem (for example in a GitHub repository) so we can find what is causing the issue. Thank you for your understanding.

heyi-let

comment created time in 5 days

issue closedvuejs/vue-cli

vue3中style的scoped不生效

Version

4.4.0

Environment info

 System:
   OS: Windows 10 10.0.18363
   CPU: (4) x64 Intel(R) Core(TM) i5-2410M CPU @ 2.30GHz
 Binaries:
   Node: 12.16.1 - D:\environment\nodejs\node.EXE
   Yarn: 1.22.4 - D:\environment\yarn\bin\yarn.CMD
   npm: 6.13.4 - D:\environment\nodejs\npm.CMD
 Browsers:
   Edge: 44.18362.449.0
 npmGlobalPackages:
   @vue/cli: Not Found

Steps to reproduce

创建项目 添加vue3支持: vue add vue-next 运行项目 打开浏览器审查元素,发现在添加了style标签scoped的,还是全局样式

What is expected?

h3[data-v-469af010] { margin: 40px 0 0; }

What is actually happening?

h3 { margin: 40px 0 0; }

<!-- generated by vue-issues. DO NOT REMOVE -->

closed time in 5 days

a644994

issue commentvuejs/vue-cli

vue3中style的scoped不生效

Fixed in vue-loader v16.0.0-beta.3

a644994

comment created time in 5 days

issue commentvuejs/vue-cli

反向代理的地址可以在打包后修改吗?方便运维管理

这个写在哪里?

sunshuaizhong

comment created time in 6 days

issue closedvuejs/vue-cli

反向代理的地址可以在打包后修改吗?方便运维管理

What problem does this feature solve?

反向代理的地址可以在打包后修改吗?方便运维管理

What does the proposed API look like?

target的地址可以放在public下面,不参与打包,打包之后可以修改

<!-- generated by vue-issues. DO NOT REMOVE -->

closed time in 6 days

sunshuaizhong

issue commentvuejs/vue-cli

反向代理的地址可以在打包后修改吗?方便运维管理

「反向代理的地址」指的是?

如果是指 devServer 的 proxy,这个跟打包是无关的; 如果是指 publicPath,参见文档 https://cli.vuejs.org/zh/config/#publicpath

这个值也可以被设置为空字符串 ('') 或是相对路径 ('./'),这样所有的资源都会被链接为相对路径,这样打出来的包可以被部署在任意路径,也可以用在类似 Cordova hybrid 应用的文件系统中。

sunshuaizhong

comment created time in 6 days

issue closedvuejs/vue-cli

List Deno as a package manager

What problem does this feature solve?

Deno is a new package manager that seems to be very hyped, It would be nice to try how well it behaves with vue-cli

What does the proposed API look like?

Add the deno executable to the dropdoen in ProjectPackageManager.js

<!-- generated by vue-issues. DO NOT REMOVE -->

closed time in 6 days

javatlacati

issue commentvuejs/vue-cli

List Deno as a package manager

Deno is not a package manager.

javatlacati

comment created time in 6 days

issue closedvuejs/vue-loader

Scoped has no effect

Version

16.0.0-beta.2

Reproduction link

https://github.com/frangio/vue-next-example

Steps to reproduce

Run npm run build and look at dist/main.css.

What is expected?

The .title style block should be scoped.

What is actually happening?

It has no scope, as if it had been just copied from the source file.

<!-- generated by vue-issues. DO NOT REMOVE -->

closed time in 6 days

frangio

issue commentvuejs/vue-loader

Regression: CSS src file produces compilation errors

Should have been fixed in beta.3. Could you have a try?

jods4

comment created time in 6 days

IssuesEvent

pull request commentvuejs/vue-loader

fix(next): use `export = xxx` instead of `exports.xxx`

Fixed in https://github.com/vuejs/vue-loader/commit/79a94dda3f2c89755ac21c4555f53b13111452bf

I chose to use ES modules to keep consistent with other modules in the repo.

The export in plugin.ts does not matter because the public API should be import { VueLoaderPlugin } from 'vue-loader' or const { VueLoaderPlugin } = require('vue-loader').

underfin

comment created time in 6 days

PR closed vuejs/vue-loader

fix(next): use `export = xxx` instead of `exports.xxx`

fix https://github.com/vuejs/vue-next/issues/1229

Bug Reson

webpack import module by node solution and caused pitcher isn't loaded. This can be fix by node exports.xxx === ts export = xxx.

+2 -2

1 comment

2 changed files

underfin

pr closed time in 6 days

issue closedvuejs/vue-loader

Scoped has no effect

Version

16.0.0-beta.2

Reproduction link

https://github.com/frangio/vue-next-example

Steps to reproduce

Run npm run build and look at dist/main.css.

What is expected?

The .title style block should be scoped.

What is actually happening?

It has no scope, as if it had been just copied from the source file.

<!-- generated by vue-issues. DO NOT REMOVE -->

closed time in 6 days

frangio

issue commentvuejs/vue-loader

Scoped has no effect

Considering it's quite a serious bug. I've released v16.0.0-beta.3 to address it. Tests will be added later in the day.

frangio

comment created time in 6 days

release vuejs/vue-loader

v16.0.0-beta.3

released time in 6 days

created tagvuejs/vue-loader

tagv16.0.0-beta.3

📦 Webpack loader for Vue.js components

created time in 6 days

push eventvuejs/vue-loader

Haoqun Jiang

commit sha a5be80eef9cfc24698769f44fdadd05190feac7d

16.0.0-beta.3

view details

push time in 6 days

push eventvuejs/vue-loader

Haoqun Jiang

commit sha 79a94dda3f2c89755ac21c4555f53b13111452bf

fix: should export the `pitch` function fixes #1677 TODO: Need to add tests later

view details

push time in 6 days

issue commentvuejs/vue-loader

Scoped has no effect

Got it. It's due to the wrong export in pitcher.ts. Will fix it tomorrow.

frangio

comment created time in 6 days

issue commentvuejs/vue-ssr-docs

官网文档,中文与 英文请不要区别对待。

既然这么有空的话,麻烦帮我们审一下这个 PR 吧,看看有没有翻译或格式问题 https://github.com/vuejs/vue-ssr-docs/pull/230

文档翻译没有更新无非两个原因:

  1. 没人翻译
  2. 有人翻译,但没人审核,所以无法合并

自己动手解决一下问题呗。

yuncode

comment created time in 6 days

issue commentvuejs/vue-cli

Prerendering not working with vue cli 4.4

Do you have a reproduction repo? It's hard for me to figure out what's going wrong without an actual project for testing, because it works fine with the default preset.

alexsonnay

comment created time in 6 days

issue closedvuejs/vue-cli

Getting error(Uncaught SyntaxError: Unexpected token '<') after "npm run serve"

Version

4.3.1

Reproduction link

https://github.com/Somnus007/vue-demo

Environment info

Environment Info:

  System:
    OS: macOS 10.15.4
    CPU: (4) x64 Intel(R) Core(TM) i5-7360U CPU @ 2.30GHz
  Binaries:
    Node: 12.16.3 - /usr/local/bin/node
    Yarn: 1.15.2 - /usr/local/bin/yarn
    npm: 6.14.5 - /usr/local/bin/npm
  Browsers:
    Chrome: 83.0.4103.61
    Edge: 80.0.361.111
    Firefox: 76.0.1
    Safari: 13.1
  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.3.1 
    @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.3.1 
    @vue/cli-plugin-babel: ~4.3.0 => 4.3.1 
    @vue/cli-plugin-eslint: ~4.3.0 => 4.3.1 
    @vue/cli-plugin-router:  4.3.1 
    @vue/cli-plugin-vuex:  4.3.1 
    @vue/cli-service: ~4.3.0 => 4.3.1 
    @vue/cli-shared-utils:  4.3.1 
    @vue/component-compiler-utils:  3.1.2 
    @vue/preload-webpack-plugin:  1.1.1 
    @vue/web-component-wrapper:  1.2.0 
    eslint-plugin-vue: ^6.2.2 => 6.2.2 
    vue: ^2.6.11 => 2.6.11 
    vue-eslint-parser:  7.1.0 
    vue-hot-reload-api:  2.3.4 
    vue-loader:  15.9.2 
    vue-style-loader:  4.1.2 
    vue-template-compiler: ^2.6.11 => 2.6.11 
    vue-template-es2015-compiler:  1.9.1 
  npmGlobalPackages:
    @vue/cli: 4.3.1

Steps to reproduce

  • vue create vue-demo
  • cd vue-demo
  • npm run serve

What is expected?

I can access to the home page with a hello world content

What is actually happening?

I got a blank page, and there is a error (Uncaught SyntaxError: Unexpected token '<') on broswer console


I created a demo by using @vue-cli 4.3.1 and have not changed any code yet. But I got a blank page after run "npm run serve"

<!-- generated by vue-issues. DO NOT REMOVE -->

closed time in 6 days

Somnus007

issue commentvuejs/vue-cli

Getting error(Uncaught SyntaxError: Unexpected token '<') after "npm run serve"

npm run serve won't serve a production service worker, neither does it come with hashed assets files. It must be due to the incorrect service worker caches brought by other projects that were previously served at localhost:8080.

So, please clear your browser service worker cache (Chrome Dev Tools -> Application -> Clear Storage -> Clear site data)

Somnus007

comment created time in 6 days

issue commentvuejs/vue-cli

Getting error(Uncaught SyntaxError: Unexpected token '<') after "npm run serve"

I'm sorry but I can't reproduce the error. Do you have a more detailed error log? What's the exact error stack and from which file did it throw?

Somnus007

comment created time in 6 days

release vuejs/vue-cli

v4.4.1

released time in 6 days

push eventvuejs/vue-cli

Roland Doda

commit sha 75017b22d90452a38bb3a37cef73070dd830e41b

docs: fix linking to npmjs.com (#5426) [ci skip]

view details

Alexander Sokolov

commit sha ba9be1c40defd195a2a77e1529c64ce6bfb4c1e9

docs: [RU] Translation update (#5384) [ci skip] Co-Authored-By: Natalia Tepluhina <tarya.se@gmail.com>

view details

Allen Zhu

commit sha ca24553983b3f6c92a12f4e2a205be739cde371d

docs(zh): fix the translation of scaffold (#5443) [ci skip]

view details

Jinzhan

commit sha 930af5f348747edee0cb9b69cfe0b65af78eb9aa

docs(zh): update ui-api.md (#5378) [ci skip]

view details

xiaohp

commit sha a9cd7838de10f70b866a2c71244d1978a3a1941c

docs(zh): update css.md (#5349) [ci skip]

view details

Alexander Sokolov

commit sha 2dbeb45f0f96a9097cd8364d0d8aaa86d463e8fe

docs: [RU] Translation update (#5468) * docs: [RU] update migrating-from-v3.md * docs: [RU] update prototyping.md * docs: [RU] update webpack.md * docs: [RU] fix typos in cli-service.md * Update docs/ru/guide/prototyping.md Co-Authored-By: Natalia Tepluhina <tarya.se@gmail.com> * docs: (ru) pwa.md update * docs: (ru) browser-compatibility.md fix import * docs: (ru) deployment.md fix example * docs: (ru) installation.md update * docs: (ru) deployment.md update link * docs: (ru) core-plugins/eslint fix * docs: (ru) pwa.md update Co-authored-by: Alex Sokolov <4497128+Alex-Sokolov@users.noreply.github.com> Co-authored-by: Natalia Tepluhina <tarya.se@gmail.com>

view details

Drew Bragg

commit sha 057201c1e80a741eb0bcda61518c6f29e1410a86

docs: explain pwa head/manifest icons (#5408)

view details

Haoqun Jiang

commit sha f425fff04f6375c4deefb6010d698d222e5141c9

chore: Merge branch 'master' into dev

view details

Haoqun Jiang

commit sha 538a0288c8a9b3c7c142c2d52c0b013f3927b85e

fix(cli): fix the creation log (#5502)

view details

Haoqun Jiang

commit sha 91ca0b1f3c67736a692f93060e22477516a332f5

refactor: improve the polyfill importing logic of modern mode (#5513) TODO: - should remove core-js from `dependencies` in the next major.

view details

Haoqun Jiang

commit sha 36b475c1172c32fba3027c4fda33d6ee4f189dfd

chore: depedency maintenance

view details

Haoqun Jiang

commit sha 34f303b0b6a03f96e8c21d308931219154a7e627

v4.4.1

view details

push time in 6 days

issue closedvuejs/vue-cli

Fedora32 support

What problem does this feature solve?

I'm using fedora32 yet I can't install vue cli-service because it doesn't support fedora32. I would also like the ability for the users to use the beta version, which can sometimes be a fix when trying to troubleshoot an app.

Error that I get:

npm http request GET https://registry.npmjs.org/@vue%2fcli-service npm ERR! Linux 5.6.12-300.fc32.x86_64 npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "i" "@vue/cli-service" npm ERR! node v7.5.0 npm ERR! npm v4.1.2 npm ERR! code EAI_AGAIN npm ERR! errno EAI_AGAIN npm ERR! syscall getaddrinfo

npm ERR! getaddrinfo EAI_AGAIN registry.npmjs.org:443 npm ERR! npm ERR! If you need help, you may report this error at: npm ERR! https://github.com/npm/npm/issues

npm ERR! Please include the following file with any support request: npm ERR! /app/npm-debug.log

What does the proposed API look like?

Just have a repo for Fedora32

<!-- generated by vue-issues. DO NOT REMOVE -->

closed time in 6 days

gawaxx

issue commentvuejs/vue-cli

Fedora32 support

The problem is not on the Vue CLI side, neither the OS version:

  1. The node / npm version is too old. Vue CLI only supports Node.js v8.9+ (and v10.12+ is recommended because v8.x has reached end-of-life).
  2. EAI_AGAIN is a network error that most likely caused by the DNS server. Please check your network setup.
gawaxx

comment created time in 6 days

push eventvuejs/vue-cli

Haoqun Jiang

commit sha 34f303b0b6a03f96e8c21d308931219154a7e627

v4.4.1

view details

push time in 6 days

created tagvuejs/vue-cli

tagv4.4.1

🛠️ Standard Tooling for Vue.js Development

created time in 6 days

push eventvuejs/jsx

Haoqun Jiang

commit sha bcf52c11e1479a21c29e07ea1b8353070516b636

docs: update vue 3 Compatibility

view details

push time in 6 days

push eventvuejs/vue-cli

Haoqun Jiang

commit sha 36b475c1172c32fba3027c4fda33d6ee4f189dfd

chore: depedency maintenance

view details

push time in 6 days

PR closed vuejs/vue-ssr-docs

docs:update zh translation
+1 -1

1 comment

1 changed file

blesstosam

pr closed time in 7 days

pull request commentvuejs/vue-ssr-docs

docs:update zh translation

这个修改没有必要,还是尊重原文更合适。

blesstosam

comment created time in 7 days

more