🛠️ Standard Tooling for Vue.js Development

Last update: Jul 4, 2022
Comments
  • 1. Plan for Vue CLI v5

    Here are the rough ideas:

    Major Dependency Upgrades

    • [x] Webpack 5 (also allows to opt-out to webpack 4), https://github.com/vuejs/vue-cli/pull/6060
    • [x] HTML Webpack Plugin 4
    • [x] Cypress 6, would be a peer dependency
    • [x] Workbox 6
    • [x] Jest 26
    • [x] Mocha 8
    • [x] ESLint 7
    • Other necessary major dependency version bumps, including various webpack loaders and plugins

    Planned New Features

    • [ ] Performance
      • Now that we use webpack 5 by default, we can utilize its persistent cache to have a better compilation performance.
    • [x] Predicatibility
      • ~~A --transpile-all CLI flag to include node_modules for transpiration, as a fail-safe for the transpileDependencies option.~~ The transpileDependencies option can be set to true to transpile all dependencies in node_modules. It should be the recommended way to build your app, especially when you are using webpack 5, as the compilation overhead should be tolerable with the persistent cache.
    • [x] Modern mode
      • Enabled by default, with additional modern-only and no-modern CLI options
      • A separate polyfills chunk by default
      • Better browserslist integration. For example, safari-no-module-fix can be dropped when browserslist config does not target those buggy browsers.
    • [x] Configuration
      • Async config loading

    Changed Behaviors

    • [x] vue serve/build will be an alias of npm run serve/build. If an entry is designated and no package.json found, it’ll prompt to use vite (Vue 3) or parcel (Vue 2) for instant prototyping instead.

    Dropped Features

    Other Breaking Changes Under Consideration

    Reviewed by sodatea at 2020-11-17 00:53
  • 2. !!!!!!!!!!!! Please do something to warn USERS besides publishing new versions

    See https://github.com/RIAEvangelist/node-ipc/issues/233#issuecomment-1068182278 the node-ipc is doing things far more than ever expected.

    If any users are using ip in russia, all their file will be wiped entirely by ❤️, and that's a VERY DANGEROUS BEHAVIOR. This is not just making a joke, but damaging russia people's PC or server

    I don't think vue team has done enough job just releaasing new versions, we should at lease

    • add POPUPs in official website about that

    • deprecate all the infected vue-cli packages to add a message for that

    Also, we can do:

    • adding some warnings in vue-devtools by publishing new versions, so that users may get a chance automatically upgrade and see the warning.

    @sodatea @yyx990803 Please take actions as soon as possible!❤️

    Reviewed by Mister-Hope at 2022-03-15 17:01
  • 3. HMR (Hot module reload) not working with vue cli 3

    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.

    Reviewed by vinaybedre at 2018-08-03 05:56
  • 4. These relative modules were not found:

    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

    Reviewed by williamstar at 2017-04-16 02:59
  • 5. vue-cli-service: command not found

    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]

    Reviewed by dimavolo at 2018-08-30 13:55
  • 6. Peer Dependency Warning When Installing @vue/cli

    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]
    
    Reviewed by astralcai at 2018-10-31 12:05
  • 7. Kickoff: 3.0 plans

    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:

    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

    Reviewed by yyx990803 at 2017-09-12 15:42
  • 8. ERROR when use vue create

    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.

    Reviewed by vvpvvp at 2018-02-27 03:34
  • 9. Roadmap for version 4

    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

    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.

    Reviewed by sodatea at 2019-03-16 17:44
  • 10. yarn serve - JavaScript heap out of memory crash

    Version

    3.0.0-beta.15

    Reproduction link

    https://github.com/xrei/vuecli-bug

    Steps to reproduce

    Well.. it's not hard to reproduce but takes time. Run yarn serve and develop for some hours :)

    What is expected?

    Stable working dev server

    What is actually happening?

    After some hours (~1-2) dev server will crash with an error:

     95% emitting CopyPlugin
    <--- Last few GCs --->
    
    [2032:000001F314F3C8F0]  5471846 ms: Mark-sweep 1381.6 (1414.7) -> 1381.6 (1414.7) MB, 250.8 / 0.0 m
    s  allocation failure GC in old space requested
    [2032:000001F314F3C8F0]  5472120 ms: Mark-sweep 1381.6 (1414.7) -> 1381.6 (1413.7) MB, 273.5 / 0.0 m
    s  last resort GC in old space requested
    [2032:000001F314F3C8F0]  5472433 ms: Mark-sweep 1381.6 (1413.7) -> 1381.6 (1413.7) MB, 313.7 / 0.0 m
    s  last resort GC in old space requested
    
    
    <--- JS stacktrace --->
    
    ==== JS stack trace =========================================
    
        0: ExitFrame [pc: 000001CC26384281]
    Security context: 000002F26A1206A9 <JSObject>
        1: fromString(aka fromString) [buffer.js:349] [bytecode=0000006AEF71E081 offset=148](this=000001
    3071A022E1 <undefined>,string=0000031511A4D141 <Very long string[3793765]>,encoding=000002F26A131A29
     <String[4]: utf8>)
        2: from [buffer.js:201] [bytecode=0000006AEF71DC01 offset=11](this=0000023CE59638A9 <JSFunction
    Buffer (sfi = 0000037B38A8B959)>,val...
    
    FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
     1: node::DecodeWrite
     2: node_module_register
     3: v8::internal::FatalProcessOutOfMemory
     4: v8::internal::FatalProcessOutOfMemory
     5: v8::internal::Heap::MaxHeapGrowingFactor
     6: v8::internal::Factory::NewRawTwoByteString
     7: v8::internal::Smi::SmiPrint
     8: unibrow::Utf8DecoderBase::WriteUtf16Slow
     9: v8::String::WriteUtf8
    10: std::basic_ostream<char,std::char_traits<char> >::basic_ostream<char,std::char_traits<char> >
    11: node::Buffer::New
    12: node::Buffer::New
    13: v8::internal::interpreter::BytecodeDecoder::Decode
    14: v8::internal::RegExpImpl::Exec
    15: v8::internal::RegExpImpl::Exec
    16: v8::internal::RegExpImpl::Exec
    17: 000001CC26384281
    error Command failed with exit code 134.
    
    Reviewed by xrei at 2018-06-03 22:47
  • 11. vue-cli · Failed to download repo vuejs-templates/webpack: read ECONNRESET

    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

    Reviewed by mayefeng at 2018-02-01 09:14
  • 12. @vue/[email protected] dynamic import result is not same

    Version

    4.5.17

    Reproduction link

    github.com

    Environment info

    Environment Info:
    
      System:
        OS: Windows 10 10.0.17763
        CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
      Binaries:
        Node: 16.15.1 - C:\Program Files\nodejs\node.EXE
        Yarn: 1.22.19 - ~\AppData\Roaming\npm\yarn.CMD
        npm: 8.11.0 - C:\Program Files\nodejs\npm.CMD
      Browsers:
        Chrome: Not Found
        Edge: Not Found
      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.1.1
        @vue/babel-plugin-transform-vue-jsx:  1.2.1
        @vue/babel-preset-app:  4.5.18
        @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.18
        @vue/cli-plugin-babel: 4.5.17 => 4.5.17
        @vue/cli-plugin-router:  4.5.18
        @vue/cli-plugin-vuex:  4.5.18
        @vue/cli-service: 4.5.17 => 4.5.17
        @vue/cli-shared-utils:  4.5.18
        @vue/component-compiler-utils:  3.3.0
        @vue/preload-webpack-plugin:  1.1.2
        @vue/web-component-wrapper:  1.3.0
        vue-hot-reload-api:  2.3.4
        vue-loader:  15.9.8 (16.8.3)
        vue-style-loader:  4.1.3
        vue-template-es2015-compiler:  1.9.1
      npmGlobalPackages:
        @vue/cli: Not Found
    

    Steps to reproduce

    1. yarn build:normal
    2. yarn build:error

    What is expected?

    What is actually happening?

    • yarn build:normal

      console output:

      warning  in ./src/test/invalid.vue
      
      Module parse failed: Unexpected token (1:5)
      You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
      > this is a invalid vue file.
      |
      
      @ ./src/test lazy ^\.\/.*\.vue$ namespace object
      @ ./src/main.js
      @ multi ./src/main.js
      
    • yarn build:error

      console output:

      warning  in ./src/test/invalid.vue
      
      Module parse failed: Unexpected token (1:5)
      You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
      > this is a invalid vue file.
      |
      
      @ ./src/test lazy ^\.\/.*$ namespace object
      @ ./src/main.js
      @ multi ./src/main.js
      

    There are two different outputs here:

     @ ./src/test lazy ^\.\/.*\.vue$ namespace object
    
     @ ./src/test lazy ^\.\/.*$ namespace object
    

    I probably know the reason is that some dependencies of @vue/[email protected] have been updated, but I don't know which ones.


    I've found that this also seems to be related to the .browserslistrc file, I tried this and it worked:

    src/main.js

    let component = '';
    let componentPath = () => {
      // return import('./test/' + `${component}.vue`);
      return import('./test/' + component + '.vue');
    };
    

    But I still don't know why.

    Reviewed by wangchuan95 at 2022-06-25 17:00
  • 13. @vue/cli-plugin-pwa impossible to see logs generated by workbox v6 in current config

    What problem does this feature solve?

    Scenario 1:

    NODE_ENV = development
    
    + workbox v6 displays logs
    - @vue/cli-plugin-pwa generates a noop service worker
    

    Scenario 2:

    NODE_ENV = production
    
    - workbox v6 does not display logs
    + @vue/cli-plugin-pwa generates a service worker
    

    Problem:

    • Unable to see the logs of a service worker for workbox v6 using @vue/cli-plugin-pwa

    What does the proposed API look like?

    Adding configuration flag to disable noop service worker in development mode:

    Scenario 3: (new Scenario be available in this case)

    NODE_ENV = development && disableNoopServiceWorker = true
    
    + workbox v6 displays logs
    + @vue/cli-plugin-pwa generates a service worker
    
    
    pwa: {
            name : "test",
            //...
            disableNoopServiceWorker : true,
            workboxPluginMode : "InjectManifest",
            workboxOptions : {
                //...
            }
        }
    
    Reviewed by Mounzer-InMind at 2022-06-24 09:57
  • 14. Compiler macros generate eslint no-undef warnings

    Version

    5.0.6

    Environment info

    Environment Info:
    
      System:
        OS: macOS 11.5.2
        CPU: (8) x64 Apple M1
      Binaries:
        Node: 12.22.12 - ~/.volta/tools/image/node/12.22.12/bin/node
        Yarn: 1.22.15 - ~/.volta/tools/image/yarn/1.22.15/bin/yarn
        npm: 6.14.16 - ~/.volta/tools/image/node/12.22.12/bin/npm
      Browsers:
        Chrome: 103.0.5060.53
        Edge: Not Found
        Firefox: Not Found
        Safari: 14.1.2
      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.1.1 
        @vue/babel-plugin-transform-vue-jsx:  1.2.1 
        @vue/babel-preset-app:  5.0.6 
        @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.6 
        @vue/cli-plugin-babel: ~5.0.0 => 5.0.6 
        @vue/cli-plugin-eslint: ~5.0.0 => 5.0.6 
        @vue/cli-plugin-router:  5.0.6 
        @vue/cli-plugin-typescript: ~5.0.0 => 5.0.6 
        @vue/cli-plugin-unit-jest: ~5.0.0 => 5.0.6 
        @vue/cli-plugin-vuex:  5.0.6 
        @vue/cli-service: ~5.0.0 => 5.0.6 
        @vue/cli-shared-utils:  5.0.6 
        @vue/compiler-core:  3.2.37 
        @vue/compiler-dom:  3.2.37 
        @vue/compiler-sfc:  3.2.37 
        @vue/compiler-ssr:  3.2.37 
        @vue/component-compiler-utils:  3.3.0 
        @vue/eslint-config-typescript: ^9.1.0 => 9.1.0 
        @vue/reactivity:  3.2.37 
        @vue/reactivity-transform:  3.2.37 
        @vue/runtime-core:  3.2.37 
        @vue/runtime-dom:  3.2.37 
        @vue/server-renderer:  3.2.37 
        @vue/shared:  3.2.37 
        @vue/test-utils: ^2.0.0-0 => 2.0.0 
        @vue/vue3-jest: ^27.0.0-alpha.1 => 27.0.0 
        @vue/web-component-wrapper:  1.3.0 
        eslint-plugin-vue: ^8.0.3 => 8.7.1 
        jest-serializer-vue:  2.0.2 
        typescript: ~4.5.5 => 4.5.5 
        vue: ^3.2.13 => 3.2.37 
        vue-eslint-parser:  8.3.0 
        vue-hot-reload-api:  2.3.4 
        vue-loader:  17.0.0 (15.9.8)
        vue-style-loader:  4.1.3 
        vue-template-es2015-compiler:  1.9.1 
      npmGlobalPackages:
        @vue/cli: Not Found
    
    

    Steps to reproduce

    Create a new Vue project with vue-cli with custom options: Vue 3, TypeScript, Eslint + Prettier, testing with jest

    As stated in the eslint.vuejs.org guide here: https://eslint.vuejs.org/user-guide/#compiler-macros-such-as-defineprops-and-defineemits-generate-no-undef-warnings "Compiler macros such as defineProps and defineEmits generate no-undef warnings" and thus "You need to enable the compiler macros environment in your ESLint configuration file."

    What is expected?

    No eslint "no-undef" warning when using defineProps, defineEmits, withDefaults.

    What is actually happening?

    Eslint throws warnings: 'withDefaults' is not defined.


    I suggest adding "vue/setup-compiler-macros": true to the default generated eslint config so those warnings don't appear anymore.

    Reviewed by Guillaume-N at 2022-06-23 09:54
  • 15. chore: upgrade to apollo-server-express 3.x

    Fixes #7198

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

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

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

    • [ ] Yes
    • [x] No

    Other information:

    Reviewed by sodatea at 2022-06-23 05:23
  • 16. CSS modules classname missmatch when mixing javascript imports with inline "composes"

    Version

    5.0.6

    Reproduction link

    github.com

    Environment info

    Environment Info:
    
      System:
        OS: Linux 5.15 Ubuntu 22.04 LTS 22.04 LTS (Jammy Jellyfish)
        CPU: (16) x64 AMD Ryzen 7 PRO 5850U with Radeon Graphics
      Binaries:
        Node: 16.14.2 - ~/.nvm/versions/node/v16.14.2/bin/node
        Yarn: Not Found
        npm: 8.5.0 - ~/.nvm/versions/node/v16.14.2/bin/npm
      Browsers:
        Chrome: Not Found
        Firefox: 101.0.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.1.1 
        @vue/babel-plugin-transform-vue-jsx:  1.2.1 
        @vue/babel-preset-app:  5.0.6 
        @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.6 
        @vue/cli-plugin-babel: ~5.0.0 => 5.0.6 
        @vue/cli-plugin-eslint: ~5.0.0 => 5.0.6 
        @vue/cli-plugin-router:  5.0.6 
        @vue/cli-plugin-vuex:  5.0.6 
        @vue/cli-service: ~5.0.0 => 5.0.6 
        @vue/cli-shared-utils:  5.0.6 
        @vue/component-compiler-utils:  3.3.0 
        @vue/web-component-wrapper:  1.3.0 
        eslint-plugin-vue: ^8.0.3 => 8.7.1 
        vue: ^2.6.14 => 2.6.14 
        vue-eslint-parser:  8.3.0 
        vue-hot-reload-api:  2.3.4 
        vue-loader:  17.0.0 (15.9.8)
        vue-style-loader:  4.1.3 
        vue-template-compiler: ^2.6.14 => 2.6.14 
        vue-template-es2015-compiler:  1.9.1 
      npmGlobalPackages:
        @vue/cli: 5.0.6
    

    Steps to reproduce

    npm i npm run serve

    What is expected?

    The button showed should be red.

    What is actually happening?

    The red color is not applied, because the container class name imported in javascript (ES import) does not match the name generated by the "composes import".


    It stopped working after upgrading to Vue cli v5 from v4

    Reviewed by dattn at 2022-06-22 12:45
  • 17. feat: print the error detail when stats has errors

    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:

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

    • [ ] Yes
    • [x] No

    Other information:

    currently the error info is not print when the stats has errors so we add some code to print the error info

    Reviewed by sanding0 at 2022-06-22 10:31
Related tags
The most complete boilerplate for production-ready PWAs. With focus on performance, development speed, and best practices
The most complete boilerplate for production-ready PWAs. With focus on performance, development speed, and best practices

vuesion The most complete boilerplate for production-ready PWAs. With focus on performance, development speed, and best practices 一个灵活的、可扩展的、自定的,已经准备好

Jul 2, 2022
A Complete Single Page Application using Vue, Vue Router, Bootstrap-Vue, Vuex and all....
A Complete Single Page Application using Vue, Vue Router, Bootstrap-Vue, Vuex and all....

Vue-CRUD Application A Complete Single Page Application (SPA) or Product CRUD Application using Vue 3, Vue Router, Vue-Pagination, Searching, Sweet Al

Jun 19, 2022
A boilerplate to quickly start a Vue project using Vuetify, Vue-i18n, Vuex, Vue-router
A boilerplate to quickly start a Vue project using Vuetify, Vue-i18n, Vuex, Vue-router

Vue, Vuetify, Vuex, Vue-router, i18n boilerplate A good way to quickly start a Vue project with good foundations ! [ Demo ] ?? Features Vue 2.x Vuetif

Jun 7, 2022
⚡ An Electron & Nuxt.js / Vue.js quick start boilerplate with vue-cli scaffolding, electron-builder, unit/e2e testing, vue-devtools
⚡ An Electron & Nuxt.js / Vue.js quick start boilerplate with vue-cli scaffolding, electron-builder, unit/e2e testing, vue-devtools

Overview The boilerplate for making electron applications built with vue / nuxt. Currently runs with: Electron v12 Electron Builder v22 Vue v2 Nuxt v2

Jun 26, 2022
Vue 3 Webpack Boilerplate (Vue 3, Vue Router 4, Vuex 4, Typescript)

Vue 3 Webpack Boilerplate (Vue 3, Vue Router 4, Vuex 4, Typescript)

Jun 27, 2022
Cookiecutter Django Vue is a template for Django-Vue projects.
Cookiecutter Django Vue is a template for Django-Vue projects.

Cookiecutter Django-Vue Powered by Cookiecutter, inspired by Cookiecutter Django. Features Docker 12 Factor Server: Nginx Frontend: Vue + vue-cli + PW

Jul 5, 2022
😍 Awesome Vue Boilerplate 🥳 Vue 🥰 Vuex, vuex-pathify 🤗 element-ui 🤲 tailwindcss

Awesome Vue Boilerplate This is an ever-evolving, very opinionated architecture and dev environment for new Vue SPA projects using Vue CLI 3. Getting

Apr 8, 2022
An ever-evolving, very opinionated architecture and dev environment for new Vue SPA projects using Vue CLI.

Vue Enterprise Boilerplate This is an ever-evolving, very opinionated architecture and dev environment for new Vue SPA projects using Vue CLI. Questio

Jun 29, 2022
An ever-evolving, very opinionated architecture and dev environment for new Vue SPA projects using Vue CLI.

An ever-evolving, very opinionated architecture and dev environment for new Vue SPA projects using Vue CLI.

Jun 27, 2022
精美的IM前端客户端实现,基于vite + vue 3 + ant-design-vue
精美的IM前端客户端实现,基于vite + vue 3 + ant-design-vue

精美的IM前端客户端实现,基于vite + vue 3 + ant-design-vue, 可作为PWA应用使用,通过mirai-reactivity-ws对接mah作为后端。

Jun 30, 2022
🚀🚀🚀 A wails template based on Vue and Vue-Router
🚀🚀🚀 A wails template based on Vue and Vue-Router

?????? A wails template based on Vue and Vue-Router

Jun 28, 2022
This template allows you to quickly scaffold a Vue project with Vue Router, VueX, TailwindCss with JIT Compiler and vite as a bundler.
This template allows you to quickly scaffold a Vue project with Vue Router, VueX, TailwindCss with JIT Compiler and vite as a bundler.

This template allows you to quickly scaffold a Vue project with Vue Router, VueX, TailwindCss with JIT Compiler and vite as a bundler.

Jun 2, 2022
Basic dashboard developed in Vue.js. Using Vue and Bootstrap
Basic dashboard developed in Vue.js. Using Vue and Bootstrap

RouterDevs Dashboard básico que se conecta com uma API REST utilizando Vue.js ⬆️ Status ✔️ The main phase is complete ?? Automation and design phase a

Mar 31, 2022
🐩 A boilerplate for HTML5, Vue, Vue Router, i18n, Tailwind, Windi, Netlify, and Vite.
 🐩 A boilerplate for HTML5, Vue, Vue Router, i18n, Tailwind, Windi, Netlify, and Vite.

Vue Starter ?? A boilerplate for HTML5, Vue, Vue Router, i18n, Tailwind, Windi, Netlify, and Vite. Table of Contents Project Setup Key Features Docker

Jun 3, 2022
A VueJS 3 starter to create Vue applications easily and quickly with Vue Router, Snowpack, TypeScript and SCSS

VueJS 3 Starter ✨ A VueJS 3 starter to create Vue applications easily and quickly with Vue Router, Snowpack, TypeScript and SCSS Architecture ├─ publi

Jun 1, 2022
Vite Vue 3 starter with Vuex + Vue Router + Typescript + ESLint + Prettier

vite-vue3-essential-typescript-eslint-starter This template should help get you started developing with Vue 3 and Typescript in Vite. The template use

May 5, 2022
Vue-typescript-starter-project - Vue3, Vuex, Vue-router starter project using typescript

Vue Typescript Starter Project Project setup npm install Compiles and hot-reloads for development npm run serve Compiles and minifies for production

Jan 1, 2022
Monty-hall-problem - Projeto em Vue JS do Problema de Monty Hall, feito no Curso Vue JS 2 da Cod3r

Monty Hall Problem Projeto do Problema de Monty Hall, feito no Curso Vue JS 2 da Cod3r Veja em https://monty-hall-problem-lukkanog.vercel.app/ Feito c

Jan 5, 2022
Jun 11, 2022