Vue CLI
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.
Vue CLI is the Standard Tooling for Vue.js Development.
Docs are available at https://cli.vuejs.org/ - we are still working on refining it and contributions are welcome!
Please see contributing guide.
Here are the rough ideas:
--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.modern-only
and no-modern
CLI optionspolyfills
chunk by defaultbrowserslist
integration. For example, safari-no-module-fix
can be dropped when browserslist
config does not target those buggy browsers.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.node-sass
See https://github.com/RIAEvangelist/node-ipc/issues/233#issuecomment-1068182278 the node-ipc
is doing things far more than ever expected.
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:
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!❤️
3.0.0-rc.10
Node 8.11.2 / Yarn 1.7.0 / Windows 10
HMR should update the browser's content based on changes made on src file
HMR is failing, any changes done to the src files are not being hot reloaded in browser.
needs team reprowhen runing dev-server there throw these two Error
ERROR Failed to compile with 2 errors 10:53:28
These relative modules were not found:
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
3.0.1
nvm 0.33.1 / Node v8.11.4 / Ubuntu 16.04
npm run build fails because vue-cli-service: command not found
npm run build succeeds
npm run build fails because vue-cli-service: command not found
Installed globally with npm install -g @vue/cli@latest
3.1.1
npm 6.4.1
npm install -g @vue/cli
Install Successful
npm WARN [email protected] requires a peer of graphql@^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 graphql@^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 graphql@^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 graphql@^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN @apollographql/[email protected] requires a peer of graphql@^0.13.1 but none is installed. You must install peer dependencies yourself.
Even after I manually install graphql with npm install -g graphql@^0.13.1, when I do npm -g list --depth=0, npm still warns
npm ERR! peer dep missing: graphql@^0.11.0 || ^0.12.0 || ^0.13.0, required by [email protected]
npm ERR! peer dep missing: graphql@^0.13.1, required by @apollographql/[email protected]
npm ERR! peer dep missing: graphql@^0.10.5 || ^0.11.3 || ^0.12.0 || ^0.13.0, required by [email protected]
npm ERR! peer dep missing: graphql@^0.13.0, required by [email protected]
npm ERR! peer dep missing: graphql@^0.13.1, required by @apollographql/[email protected]
npm ERR! peer dep missing: graphql@^0.10.5 || ^0.11.3 || ^0.12.0 || ^0.13.0, required by [email protected]
npm ERR! peer dep missing: graphql@^0.13.0, required by [email protected]
enhancement upstream scope: ui
We have been discussing an upgrade for vue-cli
for a while, in order to address a few issues in the current version.
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.
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.
[email protected]
will be moving towards a "config/scripts in a package" model, which is commonly used among several other tools:
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.
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:
A centralized entry for configuring/toggling high-level built-in features, e.g. env variables, css extraction, API proxying.
Get lower level access to the underlying webpack config and tweak it (probably with webpack-chain). This essentially works like a local preset.
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
discussion3.0.0-alpha.13
npm create test1
Please pick a preset: default (babel, eslint)
create successfull
ERROR command failed: npm install --loglevel error --registry=https://registry.npm.taobao.org --disturl=https://npm.taobao.org/dist
I choosed taobao registry, I can't change anymore.
It's time for a major version bump. This will be a relatively small release but will include a number of necessary breaking changes.
@vue/babel-preset/app
, for now we use core-js 2 by default, babel 7.4.0 supports core-js 3, once we upgraded core-js, some undocumented public APIs may change)vue-template-loader
: preserveWhitespace: false
-> whitespace: 'condense'
#3853NODE_ENV=production
by default if not specified when running vue-cli-service build
#3859plugin-pwa
: manifest.json
should be generated during the build process rather than scaffolding #2981Most proposed new features other than plugin APIs can also be landed in v3.x so they are not listed here.
vue upgrade
overhaul, allowing running codemods from pluginsvue-cli-service e2e
command (already deprecated since 3.0 rc) (#3774)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: major3.0.0-beta.15
https://github.com/xrei/vuecli-bug
Well.. it's not hard to reproduce but takes time.
Run yarn serve
and develop for some hours :)
Stable working dev server
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.
https://jsfiddle.net/b5u87965/
when create a new vue project:
vue init webpack my-project
vue-cli · Failed to download repo vuejs-templates/webpack: read ECONNRESET
init a new vue project
vue-cli · Failed to download repo vuejs-templates/webpack: read ECONNRESET
cssnano
configurable or fully controlled by postcss
See https://github.com/csstools/postcss-plugins/discussions/759
{
"css": {
"cssnano": {
"preset": [
"default",
{
"mergeLonghand": false,
"cssDeclarationSorter": false,
"colormin": false
}
]
}
}
}
I have gotten a fatal runtime error with an unmodified create-vue application.
Steps to reproduce (on my machine):
npm init vue@latest
# name "voo", typescript yes, jsx yes, vue router yes, pinia yes, testing no, eslint yes, prettier no
cd voo
npm install
npm run dev -- --port 3001
...results in a blank page and the following error in the web developer tools console:
Uncaught SyntaxError: Unexpected token '{' (at HelloWorld.vue?vue&[email protected]:2:21
The given file contains (when inspected through the developer tools), on line 2, h1[data-v-e17ea971]
, which appears to be perfectly valid CSS. However, it appears to be interpreted as JavaScript, as evidenced by the fact that when I enter valid JS at the beginning of that file and save it (at which point the dev tools attempt to re-evaluate it), the error shifts down and does not include the JS. This implies that a proximal cause of the problem is that CSS in appearing in a JavaScript context - however, I don't have the knowledge to analyze further.
Version information: Chrome, vue 3.2.45, vue-router 4.1.6, pinia 2.0.28, vite 4.0.0
What kind of change does this PR introduce? (check at least one)
Does this PR introduce a breaking change? (check one)
Other information:
Bumps express from 4.17.2 to 4.17.3.
Sourced from express's releases.
4.17.3
- deps: accepts@~1.3.8
- deps: mime-types@~2.1.34
- deps: [email protected]
- deps: [email protected]
- deps: [email protected]
- deps: [email protected]
- deps: [email protected]
- deps: [email protected]
- deps: [email protected]
- Fix handling of
__proto__
keys- pref: remove unnecessary regexp for trust proxy
Sourced from express's changelog.
4.17.3 / 2022-02-16
- deps: accepts@~1.3.8
- deps: mime-types@~2.1.34
- deps: [email protected]
- deps: [email protected]
- deps: [email protected]
- deps: [email protected]
- deps: [email protected]
- deps: [email protected]
- deps: [email protected]
- Fix handling of
__proto__
keys- pref: remove unnecessary regexp for trust proxy
3d7fce5
4.17.3f906371
build: update example dependencies6381bc6
deps: [email protected]a007863
deps: [email protected]e98f584
Revert "build: use [email protected] for Node.js < 4"a659137
tests: use strict modea39e409
tests: prevent leaking changes to NODE_ENV82de4de
examples: fix path traversal in downloads example12310c5
build: use nyc for test coverage884657d
examples: remove bitwise syntax for includes checkDependabot 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
.
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 languageYou can disable automated security fix PRs for this repo from the Security Alerts page.
5.0.8
VueCli 5.0.8,Node 18.12.1,window10
VueCli 5.0.8 修改 vue-loader 的 transformAssetUrls 选项无效,同样的修改方式在 VueCli 4.x 下可以修改成功
想修改 transformAssetUrls 选项禁止掉 vue-loader 将 img 标签的 src 属性转换为 require 功能,尝试修改后并没有禁止掉,vue-loader 仍然会将 img 的 src 特性转换为 require 调用
vue.config.js chainWebpack: (config) => { config.module.rule('vue').use('vue-loader').loader('vue-loader').tap((args) => { args.transformAssetUrls = { img: '' }; return args; }); }
VueCli 5.0.8 修改 vue-loader 的 transformAssetUrls 选项无效,同样的修改方式在 VueCli 4.x 下可以修改成功
VueCli 5.0.8 修改 vue-loader 的 transformAssetUrls 选项无效,同样的修改方式在 VueCli 4.x 下可以修改成功
@vue/cli-service
@vue/cli-ui
@vue/cli-service
devServer.server
option, avoid deprecation warnings (@backrunner, @sodatea)devServer.client.progress
@vue/cli-ui
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
)
@vue/babel-preset-app
@vue/cli-plugin-typescript
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
.
@vue/cli
@vue/cli-service
@vue/cli-plugin-e2e-cypress
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
.
@vue/cli-shared-utils
, @vue/cli-ui
node-ipc
with @achrinza/node-ipc
to further secure the dependency chain@vue/cli-service
publicPath: 'auto'
(@AndreiSoroka)@vue/cli-shared-utils
, @vue/cli-ui
node-ipc
with @achrinza/node-ipc
to further secure the dependency chain@vue/cli-shared-utils
, @vue/cli-ui
node-ipc
to v9.2.1@vue/cli-service
@vue/cli-service
@vue/cli-shared-utils
, @vue/cli-ui
node-ipc
to v9.2.1See 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:
@vue/cli-service
Backported documentation updates from the v4 branch.
Source code(tar.gz)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.
@vue/cli-plugin-typescript
, @vue/cli-service
@vue/cli-plugin-e2e-nightwatch
@vue/cli-service
@vue/cli-plugin-e2e-nightwatch
@vue/cli-ui
, @vue/cli
@vue/cli-service
@vue/cli-service
setupMiddlewares
, avoid dev server deprecation warnings (@sodatea)@vue/cli-plugin-e2e-cypress
@vue/cli
@vue/cli-service
@vue/cli-plugin-babel
, @vue/cli-plugin-eslint
, @vue/cli-plugin-pwa
, @vue/cli-plugin-typescript
, @vue/cli-service
@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
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.
latest
tag of vue
on npm becomes v3.@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
@vue/cli-plugin-eslint
, @vue/cli-ui-addon-webpack
, @vue/cli-ui-addon-widgets
, @vue/cli-ui
@vue/cli-service
@vue/cli-plugin-eslint
@vue/babel-preset-app
, @vue/cli-plugin-typescript
, @vue/cli-service
@vue/cli-service
@vue/cli-plugin-unit-jest
@vue/cli-plugin-eslint
@vue/cli-plugin-router
, @vue/cli-plugin-typescript
, @vue/cli-ui-addon-webpack
, @vue/cli-ui-addon-widgets
, @vue/cli-ui
.mjs
file type to javascript/auto
[15b1e1b]This change allows an .mjs
file to import named exports from .cjs
and plain .js
files.
Fixes compatibility with pinia
.
@vue/cli-service
@vue/cli-service
terser
option to allow users to customize the minifier (@screetBloom)@vue/cli-plugin-unit-jest
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.
Ngo Wei Lin (@Creastery) of STAR Labs (@starlabs_sg)
@vue/cli-plugin-eslint
, @vue/cli-service
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.
Ngo Wei Lin (@Creastery) of STAR Labs (@starlabs_sg)
Source code(tar.gz)@vue/cli-plugin-eslint
, @vue/cli-service
@vue/cli-plugin-e2e-webdriverio
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:
@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.@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
@vue/cli-plugin-babel
, @vue/cli-plugin-eslint
@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
@vue/cli-service
@vue/cli-plugin-pwa
, @vue/cli-service
@vue/cli-ui
For a complete guide on migrating from v4 to v5, see https://next.cli.vuejs.org/migrations/migrate-from-v4.html
jest
27 soon. Once it's done, jest
will be required as a peer dependency of @vue/cli-plugin-unit-jest
. You can add jest@26
to project dependencies now to avoid future breakages.@vue/cli-plugin-unit-jest
@vue/cli-service
@vue/cli-service
@vue/cli-plugin-unit-mocha
@vue/cli
For a complete guide on migrating from v4 to v5, see https://next.cli.vuejs.org/migrations/migrate-from-v4.html
@vue/cli-plugin-typescript
, @vue/cli-service
, @vue/cli-shared-utils
, @vue/cli
@vue/cli-plugin-pwa
@vue/cli-service
@vue/cli-plugin-unit-mocha
@vue/cli-service
@vue/cli-plugin-unit-mocha
@vue/cli-service
@vue/cli-plugin-typescript
@vue/cli-ui
@vue/cli-plugin-unit-jest
@vue/babel-preset-app
@vue/cli-plugin-unit-mocha
@vue/cli-service
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:
@vue/cli-ui-addon-webpack
, @vue/cli-ui-addon-widgets
, @vue/cli-ui
@vue/cli-plugin-webpack-4
, @vue/cli-service
@vue/cli-service
@vue/cli-plugin-babel
, @vue/cli-service
, @vue/cli-ui
@vue/cli-plugin-typescript
@vue/cli-plugin-webpack-4
, @vue/cli-service
@vue/cli-service
@vue/babel-preset-app
, @vue/cli-service
@vue/cli-plugin-babel
, @vue/cli-service
, @vue/cli-ui
@vue/cli-plugin-typescript
, @vue/cli-service
@vue/cli-ui
@vue/cli-service
@vue/cli-plugin-unit-jest
@vue/cli-plugin-unit-mocha
@vue/cli-plugin-babel
, @vue/cli-service
@vue/cli-service
@vue/cli-service
@vue/cli-plugin-unit-jest
@vue/cli-service
vue-codemod
to work around an NPM hoisting bugtypescript
version to 4.1 and prettier
version to 2.x for new projects, fixes #6299stylelint-config-standard-vue The standard shareable Vue config for Stylelint. This config: extends the stylelint-config-standard shared config and co
Vite ⚡ Next Generation Frontend Tooling ?? Instant Server Start ⚡️ Lightning Fast HMR ??️ Rich Features ?? Optimized Build ?? Universal Plugin Interfa
Phaser 3 + Vite.js Template Make Phaser 3 games with modern frontend tooling. Prerequisites You'll need Node.js and npm installed. It is highly recomm
English | 简体中文 | 日本語 | Spanish SPONSORED BY 活动服务销售平台 客户消息直达工作群 Introduction vue-element-admin is a production-ready front-end solution for admin inter
vuera NOTE: This project is looking for a maintainer! Use Vue components in your React app: import React from 'react' import MyVueComponent from './My
vue3-element-admin ?? 基于 Vite 2.0 + Vue3.0 + Vue-Router 4.0 + Vuex 4.0 + element-plus 的后台管理系统 简介 vue3-element-admin 是一个后台前端解决方案,它基于 vue3 和 element-plu
Jenesius Vue Modal Jenesius vue modal is simple library for Vue 3 only . Site Documentation Installation npm i jenesius-vue-modal For add modals in yo
Azure Static Web App Template with Node.js API This is a template repository for creating Azure Static Web Apps that comes pre-configured with: Vue.js
Mosha Vue Toastify A lightweight and fun Vue 3 toast or notification or snack bar or however you wanna call it library. English | 简体中文 Talk is cheap,
vue-cli-plugin-patch A plugin that can help you create project friendly with Vue for @vue/cli 4.5. Install First you need to install @vue/cli globally
Veloce Lightning-fast cold server start Instant hot module replacement (HMR) and dev SSR True on-demand compilation Tech Stack Vue 3: UI Rendering lib
Onsen UI - Cross-Platform Hybrid App and PWA Framework Onsen UI is an open source framework that makes it easy to create native-feeling Progressive We
Modern Vue Modern Vue stack 2022 with Micro front end & Monorepo ?? . Joyful development experience ?? . The main branch will keep clean for quickly c
Build bulletproof UI components faster Storybook is a development environment for UI components. It allows you to browse a component library, view the
A Vue.js 2.0 UI Toolkit for Web. Element will stay with Vue 2.x For Vue 3.0, we recommend using Element Plus from the same team Links Homepage and doc
Build your next Vue.js application with confidence using Nuxt: a framework making web development simple and powerful. Links ?? Documentation: https:/
Supporting Vuetify Vuetify is a MIT licensed project that is developed and maintained full-time by John Leider and Heather Leider; with support from t
Vuex ?? HEADS UP! You're currently looking at Vuex 3 branch. If you're looking for Vuex 4, please check out 4.0 branch. Vuex is a state management pat
iView A high quality UI Toolkit built on Vue.js. Docs 3.x | 2.x | 1.x Features Dozens of useful and beautiful components. Friendly API. It's made for