🛠️ Standard Tooling for Vue.js Development

Related tags

Scaffold vue-cli
Overview

Vue CLI Build Status Windows Build status lerna

Vue CLI is the Standard Tooling for Vue.js Development.

Documentation

Docs are available at https://cli.vuejs.org/ - we are still working on refining it and contributions are welcome!

Contributing

Please see contributing guide.

License

MIT

Comments
  • Plan for Vue CLI v5

    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

    opened by sodatea 114
  • !!!!!!!!!!!! Please do something to warn USERS besides publishing new versions

    !!!!!!!!!!!! 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!❤️

    opened by Mister-Hope 96
  • HMR (Hot module reload) not working with vue cli 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.

    needs team repro 
    opened by vinaybedre 92
  • These relative modules were not found:

    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

    opened by williamstar 90
  • vue-cli-service: command not found

    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]

    wontfix 
    opened by dimavolo 88
  • Peer Dependency Warning When Installing @vue/cli

    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]
    
    enhancement upstream scope: ui 
    opened by astralcai 80
  • Kickoff: 3.0 plans

    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

    discussion 
    opened by yyx990803 80
  • ERROR when use vue create

    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.

    opened by vvpvvp 67
  • Roadmap for version 4

    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.

    discussion semver: major 
    opened by sodatea 52
  • yarn serve - JavaScript heap out of memory crash

    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.
    
    opened by xrei 49
  • vue-cli · Failed to download repo vuejs-templates/webpack: read ECONNRESET

    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

    opened by mayefeng 46
  • 使用最新版的 @vue/cli-plugin-unit-jest 測試 元件內包含有 VNode 的格式會失敗

    使用最新版的 @vue/cli-plugin-unit-jest 測試 元件內包含有 VNode 的格式會失敗

    Version

    5.0.8

    Environment info

      System:
        OS: Windows 10 10.0.19045
        CPU: (6) x64 Intel(R) Core(TM) i5-8500 CPU @ 3.00GHz     
      Binaries:
        Node: 16.15.0 - C:\Program Files\nodejs\node.EXE
        Yarn: Not Found
        npm: 8.13.1 - C:\Program Files\nodejs\npm.CMD
      Browsers:
        Chrome: Not Found
        Edge: Spartan (44.19041.1266.0), Chromium (107.0.1418.52)
      npmPackages:
        @vue/babel-helper-vue-jsx-merge-props:  1.4.0 
        @vue/babel-helper-vue-transform-on:  1.0.2 
        @vue/babel-plugin-jsx:  1.1.1 
        @vue/babel-plugin-transform-vue-jsx:  1.4.0 
        @vue/babel-preset-app:  5.0.8 
        @vue/babel-preset-jsx:  1.4.0 
        @vue/babel-sugar-composition-api-inject-h:  1.4.0        
        @vue/babel-sugar-composition-api-render-instance:  1.4.0 
        @vue/babel-sugar-functional-vue:  1.4.0 
        @vue/babel-sugar-inject-h:  1.4.0 
        @vue/babel-sugar-v-model:  1.4.0 
        @vue/babel-sugar-v-on:  1.4.0 
        @vue/cli-overlay:  5.0.8
        @vue/cli-plugin-babel: ~5.0.0 => 5.0.8
        @vue/cli-plugin-eslint: ~5.0.0 => 5.0.8
        @vue/cli-plugin-router:  5.0.8
        @vue/cli-plugin-unit-jest: ^5.0.7 => 5.0.7
        @vue/cli-plugin-vuex:  5.0.8
        @vue/cli-service: ~5.0.0 => 5.0.8
        @vue/cli-shared-utils:  5.0.8
        @vue/compiler-sfc:  2.7.14
        @vue/component-compiler-utils:  3.3.0
        @vue/eslint-config-airbnb: ^6.0.0 => 6.0.0
        @vue/test-utils: ^1.1.3 => 1.3.3
        @vue/vue2-jest: ^27.0.0-alpha.3 => 27.0.0-alpha.3
        @vue/web-component-wrapper:  1.3.0
        eslint-plugin-vue: ^8.0.3 => 8.7.1
        eslint-plugin-vuejs-accessibility: ^1.1.0 => 1.2.0
        jest-serializer-vue:  2.0.2
        stylelint-config-recommended-vue: ^1.4.0 => 1.4.0
        vue: ^2.6.14 => 2.7.14
        vue-chartjs: ^4.1.1 => 4.1.2
        vue-eslint-parser:  8.3.0 (9.1.0)
        vue-hot-reload-api:  2.3.4
        vue-loader:  17.0.1 (15.10.1)
        vue-style-loader:  4.1.3
        vue-template-compiler: ^2.6.14 => 2.7.14
        vue-template-es2015-compiler:  1.9.1
      npmGlobalPackages:
        @vue/cli: Not Found
    

    Steps to reproduce

    • swiper.vue
    <template>
      <div>
        <div v-for="item in list"
             :key="item">
          <VNode :node="item.children" />
        </div>
      </div>
    </template>
    <script>
    export default {
      name: 'Swiper',
      components: {
        VNode: {
          functional: true,
          render: (_, ctx) => ctx.props.node,
        },
      },
      data() {
        return {
          list: [],
        };
      },
      mounted() {
        this.updateList();
      },
      methods: {
        updateList() {
          if (this.$slots.default && this.$slots.default.length > 0) {
            this.list = this.$slots.default.filter((vnode) => vnode.tag === 'swiper-item');
          }
        },
      },
    };
    </script>
    
    
    • test.spect.js
    describe('Swiper', () => {
      describe('@events', () => {
        it('@change - should emit a "change" event when the slide is changed', async () => {
          const wrapper = mount(Swiper);
    
          wrapper.destroy();
        });
      });
    });
    
    

    What is expected?

    測試成功

    What is actually happening?

    ● Swiper › @events › @change - should emit a "change" event when the slide is changed

    TypeError: Cannot read properties of null (reading '$createElement')
    
    > 1 | <template>
    

    原先使用 4.15.15 都是可以測試成功的 而在升到 5.0.x 版本 後都會出現錯誤 在 5.0.x 版本 把 components 底下的 VNode 拿掉就可以順利掛載上去 但由於我這個元件需要取得 slot 裡的 slot 在進行 render 故需要使用此方法

    opened by blackstuend 0
  • Built-in postcss-preset-env support

    Built-in postcss-preset-env support

    What problem does this feature solve?

    In js, vue cli has built-in '@vue/cli-plugin-babel/preset' support. It can automatically polyfill js according to the target version.

    In css, vue cli has built-in autoprefixer support. But in development, css needs more than a prefix.

    E.g:overflow: hidden auto to overflow-x: hidden;overflow-y: auto;

    https://github.com/csstools/postcss-plugins/tree/main/plugin-packs/postcss-preset-env seems to help with this.

    What does the proposed API look like?

    just like '@vue/cli-plugin-babel/preset'

    opened by DarknessChaser 0
  • Vue Cli devServer proxy for all paths is not working.  Invalid regular expression: /*/

    Vue Cli devServer proxy for all paths is not working. Invalid regular expression: /*/

    Version

    5.0.8

    Environment info

      System:
        OS: Windows 10 10.0.22621
        CPU: (12) x64 Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz
      Binaries:
        Node: 14.15.1 - C:\Program Files\nodejs\node.EXE
        Yarn: Not Found
        npm: 6.14.8 - C:\Program Files\nodejs\npm.CMD
      Browsers:
        Chrome: Not Found
        Edge: Spartan (44.22621.819.0), Chromium (106.0.1370.47)
      npmPackages:
        @progress/kendo-barcodes-vue-wrapper:  2021.3.1207
        @progress/kendo-base-components-vue-wrapper:  2021.3.1207 (2022.2.621)
        @progress/kendo-charts-vue-wrapper: 2022.2.621 => 2022.2.621
        @progress/kendo-datasource-vue-wrapper:  2022.2.621
        @progress/kendo-dateinputs-vue-wrapper: 2022.2.621 => 2022.2.621
        @progress/kendo-dropdowns-vue-wrapper: 2022.2.621 => 2022.2.621
        @progress/kendo-editor-vue-wrapper: 2022.2.621 => 2022.2.621
        @progress/kendo-inputs-vue-wrapper: 2022.2.621 => 2022.2.621
        @progress/kendo-upload-vue-wrapper: 2022.2.621 => 2022.2.621
        @progress/kendo-vue-animation: 3.3.3 => 3.3.3
        @progress/kendo-vue-buttons:  3.3.3
        @progress/kendo-vue-common:  3.3.3
        @progress/kendo-vue-data-tools: 3.3.3 => 3.3.3
        @progress/kendo-vue-dateinputs: 3.3.3 => 3.3.3
        @progress/kendo-vue-dropdowns: 3.3.3 => 3.3.3
        @progress/kendo-vue-excel-export: 3.3.3 => 3.3.3
        @progress/kendo-vue-grid: 3.3.3 => 3.3.3
        @progress/kendo-vue-indicators: 3.3.3 => 3.3.3
        @progress/kendo-vue-inputs: 3.3.3 => 3.3.3
        @progress/kendo-vue-intl: 3.3.3 => 3.3.3
        @progress/kendo-vue-labels:  3.3.3
        @progress/kendo-vue-popup: 3.3.3 => 3.3.3
        @vue/babel-helper-vue-jsx-merge-props:  1.4.0
        @vue/babel-helper-vue-transform-on:  1.0.2
        @vue/babel-plugin-jsx:  1.1.1
        @vue/babel-plugin-transform-vue-jsx:  1.4.0
        @vue/babel-preset-app:  5.0.8
        @vue/babel-preset-jsx:  1.4.0
        @vue/babel-sugar-composition-api-inject-h:  1.4.0
        @vue/babel-sugar-composition-api-render-instance:  1.4.0
        @vue/babel-sugar-functional-vue:  1.4.0
        @vue/babel-sugar-inject-h:  1.4.0
        @vue/babel-sugar-v-model:  1.4.0
        @vue/babel-sugar-v-on:  1.4.0
        @vue/cli-overlay:  5.0.8
        @vue/cli-plugin-babel: ~5.0.0 => 5.0.8
        @vue/cli-plugin-router: ~5.0.0 => 5.0.8
        @vue/cli-plugin-typescript: ~5.0.0 => 5.0.8
        @vue/cli-plugin-vuex:  5.0.8
        @vue/cli-service: ~5.0.0 => 5.0.8
        @vue/cli-shared-utils:  5.0.8
        @vue/component-compiler-utils:  3.3.0
        @vue/web-component-wrapper:  1.3.0
        bootstrap-vue: 2.22.0 => 2.22.0
        portal-vue: 2.1.7 => 2.1.7
        typescript: ~4.5.5 => 4.5.5
        vue: 2.6.14 => 2.6.14
        vue-functional-data-merge:  3.1.0
        vue-hot-reload-api:  2.3.4
        vue-loader:  17.0.1 (15.10.1)
        vue-router: 3.5.4 => 3.5.4
        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: Not Found
    

    Steps to reproduce

    `//vue.config.js

    module.exports = defineConfig({ publicPath: "./", filenameHashing: false, productionSourceMap: false, outputDir: outputDir, devServer: { server: "https", port: devServerUrl.port, host: devServerUrl.hostname, headers: { "Access-Control-Allow-Origin": "", "Access-Control-Allow-Methods": "GET, POST, PUT, DELETE, PATCH, OPTIONS", "Access-Control-Allow-Headers": "X-Requested-With, content-type, Authorization" }, proxy: { "": { // <--- here is the problem target: iisServerUrl.origin, changeOrigin: true, secure: false, cookieDomainRewrite: devServerUrl.hostname, hostRewrite: devServerUrl.host, onProxyReq: function (proxyReq, req) { var protocolWithoutColon = devServerUrl.protocol.substr(0, devServerUrl.protocol.length - 1); proxyReq.setHeader("Forwarded", host=${devServerUrl.host};proto=${protocolWithoutColon}); }, router: { [iisServerUrl.origin]: devServerUrl.origin } } } }, });`

    What is expected?

    If you write "*" or "**" in proxy the path that you wanted to be proxied, which in webpack would mean "all paths" I would get all the paths to be proxied.

    What is actually happening?

    I am getting an error: Invalid regular expression: /*/


    I ve found that Vue Cli does not support such regular expressions, and in general the api for the dev server and proxy are limited to string or objects.

    How could I write this code so it would proxy ALL requests? Thanks

    opened by danieelbog 1
  • bump loader-utils from 1.4.1 to 1.4.2

    bump loader-utils from 1.4.1 to 1.4.2

    Bumps loader-utils from 1.4.1 to 1.4.2.

    Release notes

    Sourced from loader-utils's releases.

    v1.4.2

    1.4.2 (2022-11-11)

    Bug Fixes

    Changelog

    Sourced from loader-utils's changelog.

    1.4.2 (2022-11-11)

    Bug Fixes

    Commits

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

    dependencies 
    opened by dependabot[bot] 0
  • Error after updating to typescript 4.7.X: False expression: Non-string value passed to `ts.resolveTypeReferenceDirective`

    Error after updating to typescript 4.7.X: False expression: Non-string value passed to `ts.resolveTypeReferenceDirective`

    Version

    4.5.19

    Environment info

    Environment Info:
    
      System:
        OS: Windows 10 10.0.19044
        CPU: (8) x64 Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz
      Binaries:
        Node: 16.14.2 - C:\Program Files\nodejs\node.EXE
        Yarn: Not Found
        npm: 8.5.0 - C:\Program Files\nodejs\npm.CMD
      Browsers:
        Chrome: 106.0.5249.119
        Edge: Spartan (44.19041.1266.0), Chromium (107.0.1418.42)
      npmPackages:
        @vue/babel-helper-vue-jsx-merge-props:  1.4.0
        @vue/babel-helper-vue-transform-on:  1.0.2
        @vue/babel-plugin-jsx:  1.1.1
        @vue/babel-plugin-transform-vue-jsx:  1.4.0
        @vue/babel-preset-app:  4.5.19
        @vue/babel-preset-jsx:  1.4.0
        @vue/babel-sugar-composition-api-inject-h:  1.4.0
        @vue/babel-sugar-composition-api-render-instance:  1.4.0
        @vue/babel-sugar-functional-vue:  1.4.0
        @vue/babel-sugar-inject-h:  1.4.0
        @vue/babel-sugar-v-model:  1.4.0
        @vue/babel-sugar-v-on:  1.4.0
        @vue/cli-overlay:  4.5.19
        @vue/cli-plugin-babel: ~4.5.19 => 4.5.19
        @vue/cli-plugin-eslint: ~4.5.19 => 4.5.19
        @vue/cli-plugin-router:  4.5.19
        @vue/cli-plugin-typescript: ~4.5.19 => 4.5.19
        @vue/cli-plugin-unit-mocha: ~4.5.19 => 4.5.19
        @vue/cli-plugin-vuex: ~4.5.19 => 4.5.19
        @vue/cli-service: ~4.5.19 => 4.5.19
        @vue/cli-shared-utils:  4.5.19
        @vue/component-compiler-utils:  3.3.0
        @vue/composition-api: ^1.7.1 => 1.7.1
        @vue/devtools-api:  6.4.5
        @vue/eslint-config-prettier: ~6.0.0 => 6.0.0
        @vue/eslint-config-typescript: ~11.0.2 => 11.0.2
        @vue/preload-webpack-plugin:  1.1.2
        @vue/test-utils: ~1.3.3 => 1.3.3
        @vue/web-component-wrapper:  1.3.0
        eslint-plugin-vue: ~9.7.0 => 9.7.0
        typescript: 4.7.4 => 4.7.4
        vue: ~2.6.14 => 2.6.14
        vue-class-component: ~7.2.6 => 7.2.6
        vue-demi:  0.13.11
        vue-eslint-parser:  9.1.0
        vue-hot-reload-api:  2.3.4
        vue-loader:  15.10.1 (16.8.3)
        vue-property-decorator: ~9.1.2 => 9.1.2
        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: Not Found
    
    

    Steps to reproduce

    npm run serve

    What is expected?

    No errors while serving the client

    What is actually happening?

    INTERNAL ERROR(undefined,undefined) Debug Failure. False expression: Non-string value passed to `ts.resolveTypeReferenceDirective`, likely by a wrapping package working with an outdated `resolveTypeReferenceDirectives` signature.
     This is probably not a problem in TS itself.
    stack trace:
    Error: Debug Failure. False expression: Non-string value passed to `ts.resolveTypeReferenceDirective`, likely by a wrapping package working with an outdated `resolveTypeReferenceDirectives` signature. This is probably not a problem in TS itself.
        at Object.resolveTypeReferenceDirective (C:\repos\myClient\node_modules\typescript\lib\typescript.js:42537:18)
        at resolveTypeReferenceDirective (C:\repos\myClient\node_modules\fork-ts-checker-webpack-plugin\lib\resolution.js:20:35)
        at C:\repos\myClient\node_modules\fork-ts-checker-webpack-plugin\lib\VueProgram.js:81:24
        at Array.map (<anonymous>)
        at Object.host.resolveTypeReferenceDirectives (C:\repos\myClient\node_modules\fork-ts-checker-webpack-plugin\lib\VueProgram.js:80:39)
        at actualResolveTypeReferenceDirectiveNamesWorker (C:\repos\myClient\node_modules\typescript\lib\typescript.js:116674:163)
        at resolveTypeReferenceDirectiveNamesWorker (C:\repos\myClient\node_modules\typescript\lib\typescript.js:116974:26)
        at processTypeReferenceDirectives (C:\repos\myClient\node_modules\typescript\lib\typescript.js:118456:31)
        at findSourceFileWorker (C:\repos\myClient\node_modules\typescript\lib\typescript.js:118341:21)
        at findSourceFile (C:\repos\myClient\node_modules\typescript\lib\typescript.js:118196:26)
    Version: typescript 4.7.4
    Time: 1780ms
    

    In my Vue 2 project I updated typescript from 4.6 to 4.7. Serving my app throw this error in the console.

    opened by wal0x 1
Releases(v5.0.8)
  • v5.0.8(Jul 7, 2022)

    :bug: Bug Fix

    • @vue/cli-service
      • 0260e4d fix: add devServer.server.type to useHttps judgement (https://github.com/vuejs/vue-cli/pull/7222)
    • @vue/cli-ui
      • 07052c4 fix: Vue CLI UI graphql subscription server error, fixes https://github.com/vuejs/vue-cli/issues/7221
    Source code(tar.gz)
    Source code(zip)
  • v5.0.7(Jul 5, 2022)

  • v4.5.19(Jun 28, 2022)

    IMPORTANT NOTE: IE 11 has reached End-of-Life. The default browserslist query no longer includes IE 11 as a target. If your project still has to support IE 11, you MUST manually add IE 11 to the last line of the .browserslistrc file in the project (or browserslist field in package.json)

    :bug: Bug Fix

    • @vue/babel-preset-app
      • [c7fa1cf] fix: always transpile syntaxes introduced in ES2020 or later, so that optional chaining and nullish coalescing syntaxes won't cause errors in webpack 4 and ESLint 6.
    • @vue/cli-plugin-typescript
      • [5b57792] fix: typechecking with Vue 2.7, fixes #7213
    Source code(tar.gz)
    Source code(zip)
  • v5.0.6(Jun 16, 2022)

    Fix compatibility with the upcoming Vue 2.7 (currently in alpha) and Vue Loader 15.10 (currently in beta).

    In Vue 2.7, vue-template-compiler is no longer a required peer dependency. Rather, there's a new export under the main package as vue/compiler-sfc.

    Source code(tar.gz)
    Source code(zip)
  • v5.0.5(Jun 16, 2022)

    :bug: Bug Fix

    • @vue/cli
      • #7167 fix(upgrade): prevent changing the structure of package.json file during upgrade (@blzsaa)
    • @vue/cli-service
    • @vue/cli-plugin-e2e-cypress
      • [697bb44] fix: should correctly resolve cypress bin path for Cypress 10 (Note that the project is still created with Cypress 9 by default, but you can upgrade to Cypress 10 on your own now)

    Committers: 3

    Source code(tar.gz)
    Source code(zip)
  • v4.5.18(Jun 16, 2022)

    Fix compatibility with the upcoming Vue 2.7 (currently in alpha) and Vue Loader 15.10 (currently in beta).

    In Vue 2.7, vue-template-compiler is no longer a required peer dependency. Rather, there's a new export under the main package as vue/compiler-sfc.

    Source code(tar.gz)
    Source code(zip)
  • v4.5.17(Mar 23, 2022)

  • v5.0.4(Mar 22, 2022)

  • v5.0.3(Mar 15, 2022)

  • v5.0.2(Mar 15, 2022)

  • v4.5.16(Mar 15, 2022)

    4.5.16 (2022-03-15)

    :bug: Bug Fix

    • @vue/cli-service
      • Fix demo-lib.html and demo-wc.html for Vue 2
    • @vue/cli-shared-utils, @vue/cli-ui
      • Lock node-ipc to v9.2.1
    Source code(tar.gz)
    Source code(zip)
  • v5.0.1(Feb 17, 2022)

    See https://cli.vuejs.org/migrations/migrate-from-v4.html for a complete list of breaking changes from v4.


    v5.0.0 was skipped due to a network failure when releasing the packages.


    Changes since v5.0.0-rc.3:

    :bug: Bug Fix

    :memo: Documentation

    Backported documentation updates from the v4 branch.

    Source code(tar.gz)
    Source code(zip)
  • v5.0.0-rc.3(Feb 10, 2022)

    This is likely to be the last RC version of Vue CLI 5. No more breaking changes are planned. If no major regressions occur, a stable version will be released in a week.

    :boom: Breaking Changes

    • @vue/cli-plugin-typescript, @vue/cli-service
    • @vue/cli-plugin-e2e-nightwatch

    :rocket: New Features

    • @vue/cli-service
    • @vue/cli-plugin-e2e-nightwatch

    :bug: Bug Fix

    • @vue/cli-ui

    Committers: 6

    Source code(tar.gz)
    Source code(zip)
  • v5.0.0-rc.2(Jan 15, 2022)

    :boom: Breaking Changes

    • @vue/cli-ui, @vue/cli
      • #6917 feat!: make Vue 3 the default version for vue create (@sodatea)
    • @vue/cli-service

    :bug: Bug Fix

    • @vue/cli-service
      • #6944 fix: set mini-css-extract-plugin to 2.4.5 (@cexbrayat)
      • #6907 fix: use setupMiddlewares, avoid dev server deprecation warnings (@sodatea)
    • @vue/cli-plugin-e2e-cypress

    Committers: 3

    Source code(tar.gz)
    Source code(zip)
  • v5.0.0-rc.1(Nov 17, 2021)

    :rocket: New Features

    :bug: Bug Fix

    • @vue/cli-service
      • #6826 fix: [ext] in asset modules already contains a leading dot (@sodatea)
    • @vue/cli-plugin-babel, @vue/cli-plugin-eslint, @vue/cli-plugin-pwa, @vue/cli-plugin-typescript, @vue/cli-service

    :memo: Documentation

    • @vue/cli-plugin-babel, @vue/cli-plugin-e2e-cypress, @vue/cli-plugin-e2e-nightwatch, @vue/cli-plugin-e2e-webdriverio, @vue/cli-plugin-eslint, @vue/cli-plugin-pwa, @vue/cli-plugin-router, @vue/cli-plugin-typescript, @vue/cli-plugin-unit-jest, @vue/cli-plugin-unit-mocha, @vue/cli-plugin-vuex

    Committers: 3

    Source code(tar.gz)
    Source code(zip)
  • v5.0.0-rc.0(Nov 6, 2021)

    For a complete guide on migrating from v4 to v5, see https://next.cli.vuejs.org/migrations/migrate-from-v4.html

    There are still a few planned breaking changes that we are still working on. But most features are stable. So we think now is a good time for a release candidate.

    • Default preset will be the Vue 3 preset, once the latest tag of vue on npm becomes v3.
    • There are a few major upstream dependencies that we may upgrade to once they are ready. Please be aware of the possible breaking changes if your custom configuration depends on them:
      • The default mocha version in @vue/cli-plugin-unit-mocha is still mocha 8 because mocha 9 isn't yet supported in mochapack.
      • fork-ts-checker-webpack-plugin doesn't support type checking <script setup> blocks yet. For now, you have to run vue-tsc separately. The feature is being actively worked on, though.

    The following are the changes between 5.0.0-beta.7 and 5.0.0-rc.0:

    • @vue/cli
      • #6817 feat: generate vue.config.js with defineConfig wrapper (@sodatea)
    • @vue/cli-plugin-eslint, @vue/cli-ui-addon-webpack, @vue/cli-ui-addon-widgets, @vue/cli-ui
      • #6795 feat(generator)!: bump eslint-plugin-vue to v8 (@sodatea)
    • @vue/cli-service
      • #6790 feat!: bump css-loader and mini-css-extract-plugin versions (@sodatea)
    • @vue/cli-plugin-eslint
      • #6791 feat: replace@vue/eslint-config-prettier with eslint-config-prettier (@sodatea)

    :boom: Breaking Changes

    • @vue/babel-preset-app, @vue/cli-plugin-typescript, @vue/cli-service
      • #6808 feat!: remove @vue/compiler-sfc from peer dependencies (@sodatea)
    • @vue/cli-service
      • #6790 feat!: bump css-loader and mini-css-extract-plugin versions (@sodatea)

    :bug: Bug Fix

    • @vue/cli-plugin-unit-jest
    • @vue/cli-plugin-eslint
      • #6787 fix: bump eslint-webpack-plugin and fix lintOnError regressions (@sodatea)

    :house: Internal

    • @vue/cli-plugin-router, @vue/cli-plugin-typescript, @vue/cli-ui-addon-webpack, @vue/cli-ui-addon-widgets, @vue/cli-ui
      • #6809 refactor: use multi-word names for router views (@sodatea)

    Committers: 3

    Source code(tar.gz)
    Source code(zip)
  • v4.5.15(Oct 28, 2021)

  • v5.0.0-beta.7(Oct 26, 2021)

    :boom: Breaking Changes

    • @vue/cli-service
      • #6771 feat!: remove url-loader and file-loader in favor of asset modules (@sodatea)
      • #6781 fix!: set hashFunction to xxhash64 to fix Node 17 compatibility (@sodatea)

    :rocket: New Features

    • @vue/cli-service
      • #6752 Add a top-level terser option to allow users to customize the minifier (@screetBloom)

    :bug: Bug Fix

    Committers: 3

    Source code(tar.gz)
    Source code(zip)
  • v5.0.0-beta.6(Oct 14, 2021)

    Security Fixes

    This version fixed a CORS vulnerability and an XSS vulnerability in Vue CLI UI. We recommend all users of vue ui to upgrade to this version as soon as possible.

    Credits:

    Ngo Wei Lin (@Creastery) of STAR Labs (@starlabs_sg)

    New Features

    • @vue/cli-plugin-eslint, @vue/cli-service

    Committers: 1

    Source code(tar.gz)
    Source code(zip)
  • v4.5.14(Oct 14, 2021)

  • v5.0.0-beta.5(Oct 10, 2021)

  • v5.0.0-beta.4(Sep 15, 2021)

    For a complete guide on migrating from v4 to v5, see https://next.cli.vuejs.org/migrations/migrate-from-v4.html

    Upcoming breaking changes in the next beta:

    • As WebDriverIO's sync API has been deprecated and doesn't work in Node.js v16, we are going to remove @wdio/sync from the dependencies of @vue/cli-plugin-e2e-webdriverio. Please be prepared and migrate to the async API, or install the @wdio/sync package in the projects by yourselves.

    :boom: Breaking Changes

    • @vue/cli-plugin-typescript, @vue/cli-plugin-unit-jest
    • @vue/cli-plugin-eslint, @vue/cli-service, @vue/cli-test-utils
    • @vue/cli-plugin-e2e-cypress
      • #6662 feat!: update cypress to 8.3 and require it to be a peer dependency (@sodatea)

    :rocket: New Features

    • @vue/cli-plugin-babel, @vue/cli-plugin-eslint
      • #6663 feat: generate projects with transpileDependencies: true by default (@sodatea)
    • @vue/cli-plugin-typescript, @vue/cli-plugin-unit-jest
    • @vue/cli-plugin-eslint, @vue/cli-service, @vue/cli-test-utils
    • @vue/cli-plugin-e2e-cypress
      • #6662 feat!: update cypress to 8.3 and require it to be a peer dependency (@sodatea)

    :bug: Bug Fix

    • @vue/cli-service
      • #6665 fix: avoid copy-webpack plugin errors in module mode (@sodatea)
      • #6645 fix(cli-service): wrong property name (typo) (@Vinsea)

    :memo: Documentation

    • #6653 docs: recommend SFC playground and StackBlitz for instant prototyping (@sodatea)

    :house: Internal

    • @vue/cli-plugin-pwa, @vue/cli-service
    • @vue/cli-ui

    Committers: 4

    Source code(tar.gz)
    Source code(zip)
  • v5.0.0-beta.3(Aug 10, 2021)

    For a complete guide on migrating from v4 to v5, see https://next.cli.vuejs.org/migrations/migrate-from-v4.html

    Note on Future Betas

    • We'll upgrade to jest 27 soon. Once it's done, jest will be required as a peer dependency of @vue/cli-plugin-unit-jest. You can add [email protected] to project dependencies now to avoid future breakages.

    :boom: Breaking Changes

    • @vue/cli-plugin-webpack-4, @vue/cli-service

    :rocket: New Features

    • @vue/cli-plugin-unit-jest
      • #6625 feat(unit-jest): add jest as a peer dependency (@sodatea)
    • @vue/cli-service

    :bug: Bug Fix

    • @vue/cli-service
      • #6597 fix: mark sideEffects: true for styles in Vue components (@sodatea)
    • @vue/cli-plugin-unit-mocha
      • #6560 fix(mocha): do not ignore JavaScript tests when TypeScript plugin is installed (@j-a-m-l)

    :memo: Documentation

    Committers: 4

    Source code(tar.gz)
    Source code(zip)
  • v5.0.0-beta.2(Jun 9, 2021)

    For a complete guide on migrating from v4 to v5, see https://next.cli.vuejs.org/migrations/migrate-from-v4.html

    :rocket: New Features

    • @vue/cli-plugin-typescript, @vue/cli-service, @vue/cli-shared-utils, @vue/cli

    :bug: Bug Fix

    • @vue/cli-plugin-pwa
      • #6518 fix(pwa): Replace closeTag parameter with voidTag for HtmlWebpackPlugin (@tcitworld)
    • @vue/cli-service
    • @vue/cli-plugin-unit-mocha
      • #6478 fix(mocha): set mode to none to avoid DefinePlugin conflict (@sodatea)

    :memo: Documentation

    :house: Internal

    • @vue/cli-service

    Committers: 6

    Source code(tar.gz)
    Source code(zip)
  • v5.0.0-beta.1(May 19, 2021)

    :rocket: New Features

    • @vue/cli-service
    • @vue/cli-plugin-unit-mocha

    :boom: Breaking Changes

    • @vue/cli-ui
      • #6443 fix!: keep project name validation rules in sync between UI and CLI (@sodatea)

    :bug: Bug Fix

    • @vue/cli-service
      • #6470 fix(SafariNomoduleFixPlugin): use RawSource instead of a plain object (@KaelWD)
    • @vue/cli-plugin-typescript
      • #6456 fix(typescript): add missing dependencies and require.resolve compiler (@merceyz)
    • @vue/cli-ui
      • #6443 fix!: keep project name validation rules in sync between UI and CLI (@sodatea)
    • @vue/cli-plugin-unit-jest

    Committers: 4

    Source code(tar.gz)
    Source code(zip)
  • v4.5.13(May 8, 2021)

  • v5.0.0-beta.0(Apr 25, 2021)

    For a complete guide on migrating from v4 to v5, see https://next.cli.vuejs.org/migrations/migrate-from-v4.html


    The following are the changes between 5.0.0-alpha.8 and 5.0.0-beta.0:

    :boom: Breaking Changes

    • @vue/cli-ui-addon-webpack, @vue/cli-ui-addon-widgets, @vue/cli-ui
    • @vue/cli-plugin-webpack-4, @vue/cli-service
      • #6420 feat!: upgrade to css-minimizer-webpack-plugin v2 (@sodatea)
    • @vue/cli-service
      • #6422 feat!: always inject safari-nomodule-fix as an external script; drop --no-unsafe-inline flag (@sodatea)
    • @vue/cli-plugin-babel, @vue/cli-service, @vue/cli-ui
      • #6416 feat!: turn on modern mode by default, and provide a --no-module option (@sodatea)

    :rocket: New Features

    • @vue/cli-plugin-typescript
    • @vue/cli-plugin-webpack-4, @vue/cli-service
      • #6420 feat!: upgrade to css-minimizer-webpack-plugin v2 (@sodatea)
    • @vue/cli-service
      • #6422 feat!: always inject safari-nomodule-fix as an external script; drop --no-unsafe-inline flag (@sodatea)
      • #6285 feat(cli-service): provide jsconfig.json in no-ts template (@yoyo930021)
      • #5997 feat(cli-service): add inline loader support for html-webpack-plugin (@ylc395)
    • @vue/babel-preset-app, @vue/cli-service
      • #6419 feat: only needs one bundle if all targets support es module (@sodatea)
    • @vue/cli-plugin-babel, @vue/cli-service, @vue/cli-ui
      • #6416 feat!: turn on modern mode by default, and provide a --no-module option (@sodatea)
    • @vue/cli-plugin-typescript, @vue/cli-service

    :bug: Bug Fix

    • @vue/cli-ui
    • @vue/cli-service
    • @vue/cli-plugin-unit-jest
      • #6418 Show fallback message for typescript jest preset if ts-jest is not in… (@m0ksem)
    • @vue/cli-plugin-unit-mocha

    :memo: Documentation

    • #6438 docs: add modern mode changes to the migration guide (@sodatea)

    Committers: 8

    Source code(tar.gz)
    Source code(zip)
  • v5.0.0-alpha.8(Mar 24, 2021)

    :rocket: New Features

    • @vue/cli-plugin-babel, @vue/cli-service
      • #6354 feat: when transpileDependencies is set to true, transpile all dependencies in node_modules (@sodatea)
    • @vue/cli-service
      • #6355 feat: a defineConfig API from @vue/cli-service for better typing support in vue.config.js (@sodatea)

    :boom: Breaking Changes

    • @vue/cli-service
    • @vue/cli-plugin-unit-jest
      • #6347 refactor!: move vue-jest and ts-jest to peer dependencies (@sodatea)

    :bug: Bug Fix

    • @vue/cli-service

    Committers: 4

    Source code(tar.gz)
    Source code(zip)
  • v4.5.12(Mar 17, 2021)

    • bump vue-codemod to work around an NPM hoisting bug
    • bump minimum required JSX preset / plugin versions, fixes https://github.com/vuejs/jsx/issues/183
    • bump default typescript version to 4.1 and prettier version to 2.x for new projects, fixes #6299
    Source code(tar.gz)
    Source code(zip)
  • v5.0.0-alpha.7(Mar 11, 2021)

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 一个灵活的、可扩展的、自定的,已经准备好

vuesion 2.6k Nov 22, 2022
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

Maniruzzaman Akash 55 Oct 11, 2022
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

Morgän 13 Nov 21, 2022
⚡ 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

Michał Zarach 672 Nov 24, 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)

Vlad Starkovsky 72 Oct 11, 2022
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

Viktor Chaptsev 547 Nov 22, 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

Narek Hakobyan 61 Oct 20, 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

Ben Hong 7.6k Nov 25, 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.

Ben Hong 7.6k Dec 3, 2022
精美的IM前端客户端实现,基于vite + vue 3 + ant-design-vue

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

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

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

misitebao 119 Nov 18, 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.

VivekAsCoder 57 Jul 5, 2022
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

Beatriz gonçalves 4 Mar 31, 2022
🐩 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

Shyam Chen 148 Nov 20, 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

null 1 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

유안씌 12 Aug 12, 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

paalan 0 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

Lucas Nogueira de Souza 0 Jan 5, 2022
null 40 Nov 7, 2022