Roadmap for version 4

[haoqunjiang]

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

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

Changed Behavior

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

New Features

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

• Plugin API: Allow plugins to provide a minimum vue-cli version feat: add .version field and assertVersion helper to plugin api #3861
• vue upgrade overhaul, allowing running codemods from plugins
• Plugin ordering Hook to act after others plugins invocation #1754, Plugin depending on another plugin #1938

Removed

• Drop Node.js v9 support (in documentation, no need to touch the code)
• remove support for vue-cli-service e2e command (already deprecated since 3.0 rc) (chore: remove support for legacy vue-cli-service e2e command #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
• Use mochapack instead of mocha-webpack
• 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.

[edimitchel]

Mocha is much faster than Jest. Keep it.

[NeiPCs]

Yep, since we know what breaking changes will apply, we can work on documentation of migration from X to Y version.

[LinusBorg]

Mocha is much faster than Jest. Keep it.

We would, if someone can assure us mocha-webpack will continue to work with webpack 5 even though it's currently unmaintained.

Otherwise we just keep a feature alive that is destined to die soon anyway.

[salvadordiaz]

There is a fork of mocha-webpack that works with webpack 4 and mocha 4, 5 and 6:
https://github.com/sysgears/mochapack

I really hope that we can avoid having to migrate our test suite from mocha to jest.

[Garito]

My 5 cents: the simpler the better

[LinusBorg]

@salvadordiaz That looks promising, assuming the author is up to upgrade it to webpack 5 compatibility when that time arrives.

[geedew]

Is there a discussion ticket for the Codemods work?

[LinusBorg]

Nope. Also, we should probably do a real RFC for his as the vue-cli repo is one of the repos we included for the official RFC process in https://github.com/vuejs/rfcs#when-to-follow-this-process

We might discuss possibly deprecating mocha there as well, as it's likely a hot topic.

[yannick-milanetto]

Is there any plans to support server-side rendering in core, without having to go for a 3rd party plugin ?

[larixer]

@LinusBorg Hi, I'm the maintainer of mochapack. Is Webpack 5 support is the only thing you need to continue using mocha unit tests and mocha-webpack, or have you made a decision to drop mocha tests in favor of jest already?

[LinusBorg]

@Vlasenko Hi 😁

We haven't made that decision, that's what this issue is meant to discuss.

We don't want to "get rid" of mocha. Until someone mentioned your fork, we just didn't see any future for it since mocha webpack was unmaintained.

So if you ate panning to keep on working on mochapack and make it work with webpack 5, my opinion would be to keep it 🙂

[larixer]

@LinusBorg Great! Yes, I plan to keep on working on mochapack and add Wepback 5 support to it. I will notify you here, when Webpack 5 support will be ready in mochapack.

[cngu]

@LinusBorg Hi! Based on the discussion here #947 (comment), has an alternative for inject-loader been investigated yet?

If not, Jest has some complimentary features to help replace inject-loader that you may want to consider when comparing it with Mocha.

[pksunkara]

Thanks for creating this @sodatea and @LinusBorg. It's good to see the development of this repo is more transparent now. I can work on the new features (some of it already done) since I was the one who was requesting them mostly. We can discuss more if you guys want. I will be available in the Vue Discord.

[pksunkara]

@geedew

Is there a discussion ticket for the Codemods work?

There is some discussion about the scenarios that need to be handled in #1507 when the original work for vue-upgrade has been done.

For an example issue that rose up because vue-upgrade is not properly done is in storybook plugin linked here

[KyLeoHC]

Think about replacing tslint with typescript-eslint.And replace ts-loader with babel7.

[LinusBorg]

replacing tslint with typescript-eslint

We will do that once typescript-eslint has the announced feature parity with tslint.

And replace ts-loader with babel7.

Since babel's typescript implementation comes with some significant limitations we probably won't do that.

[andreiTn]

TSLint doesn't detect HTML errors inside .
Steps to reproduce:

1. Create a new Vue project with Typescript and TSLint.
2. Create an error inside HTML in a .vue file. For example, remove an angle bracket < from a tag.
3. Run yarn lint

Output: No lint errors found!

ESLin detects this, however, I don't know if I should use ESLint with Typescript or ESLint together with TSLint. Is this something that you could look into for the next version?

[IndexXuan]

@andreiTn you should use eslint with ts，since it support ts and will support by the core ts team in the futher. tslint is deprecated！

[andreiTn]

Thanks @IndexXuan

[752]

update html-webpack-plugin to 4.x ?
jantimon/html-webpack-plugin#878
jantimon/html-webpack-plugin#1069

[LinusBorg]

Sure, once it's out of beta (currently: 4.0.0-beta.5)

[alvarosabu]

Have you guys ever thought about adding commands for scaffolding, to easily create views, components, stores? Similar to https://github.com/hjeti/vue-generator. You can also create a directory with your own templates (with your code conventions) inside of your project.

[moranje]

Hope you are aware of:

https://eslint.org/docs/6.0.0/user-guide/migrating-to-6.0.0

[ashleynolan]

Are there any plans to add ES6 module output to the library build mode in a future version of vue-cli?

[haoqunjiang]

@ashleynolan pending webpack/webpack#2933

[ffxsam]

Another vote to get rid of the TSLint option in vue-cli, as it's being deprecated. I've replaced it in one of my projects with the new TypeScript ESLint plugin, and does just fine validating my code.

Full ruleset here.

EDIT: If TSLint must remain, perhaps the inclusion of a deprecation warning would be a good idea.

[haoqunjiang]

@ffxsam PR submitted #4289

[bodograumann]

I see the “vue upgrade” item is marked done. There are some open in points in #4090 though. Most importantly there is no documentation for the MigrationAPI.

Secondly, the linked tickets for “plugin ordering” are resolved by #2337. Is there anything else planned for 4.0?

Finally, any predictions on a release date?

[haoqunjiang]

For the vue upgrade command:
It still needs refinement, but is usable. So it won't block v4 stable release, we can do the refinement in later feature releases.

The MigratorAPI:
It's the same as GeneratorAPI with an additional fromVersion(range) method. I'm working on the documentation.

Plugin Ordering:
Not fully resolved, but the most common concerns have been addressed and I believe most use cases can be solved or worked around with the latest API.
No major new features planned as of now.

Release date:
v4 is now in beta, meaning it's mostly usable with maybe a few glitches. Feedbacks are welcome.

The next step is to fix noticeable bugs and to refine the documentation.
Actually, I'm working on a blog post to introduce its major changes but haven't got the time to finish it.
I'd like to complete the beta and then rc phase in the coming weeks, but this is not set in stone, in case any major issues encountered during the test.

[falstack]

Multiple Component Lib support.

src dir

// src
-- componentA
  |-- index.js
  |-- a.vue
-- componentB
  |-- index.js
  |-- b.vue

build script

"build": "vue-cli-service build --target lib --name myLib 'src/**/index.js'"

output dir

// dist
myLib.xxx.js
myLib.min.css
componentA
  |-- index.js
  |-- style.css
componentB
  |-- index.js
  |-- style.css

[bodograumann]

typescript-eslint version 2.0.0 was just released!
Lots of changes; probably requires modifying @vue/eslint-config-typescript. Oh, just seeing that that has been moved to its own repository. So not sure how you want to handle this.

[pksunkara]

eslint-config-airbnb 14.0.0 released to be in line with eslint 6

[haoqunjiang]

ESLint config versions are managed separately from @vue/cli-plugin-eslint.
If they have new versions, the default config versions used for generating new projects will be bumped in a minor release of the plugin.

I'd also like to implement an upgrade hook in the plugin, to prompt the user to optionally update the config version and its peer dependencies. This feature may or may not land in 4.0 because it seems not that urgent.

[bodograumann]

I would love to see that, @sodatea. I often have the problem that npm update installs a new version of typescript but @typescript-eslint/* are not updated. That leads to the usual “typescript version not supported” warning and to linting issues. Of course I can fix it with a deep update, but a more care-free solutions would be much appreciated.

[linden5]

How about supporting running vue-cli-service programatically by passing in user options?

[LinusBorg]

Not sure what exactly you mean by that ...?

[linden5]

Not sure what exactly you mean by that ...?

The method "run" of vue-cli-service currently accepts three arguments: command, args, rawArgv. If there is a method to run the service by passing in a config object and an array of plugins, it would be more convenient for users who want to build their own cli tools based on vue-cli-service and put all config files in the very pakcage (Actually I have been assigned such a task, and want to reuse the webpack configuration of vue-cli-service). The method may be called like this:

const vueConfig = require('vue.config.js')
const plugins = [
    require('@vue/cli-plugin-babel'),
    require('@vue/cli-plugin-eslint'),
    require('@vue/cli-plugin-unit-jest')
]
service.run(vueConfig, plugins)

Now, in order to make my cli tool work, I have to set the
environment variables VUE_CLI_CONTEXT and VUE_CLI_SERVICE_CONFIG_PATH, as well as manully constructing args and rawArgv the "run" method needs. This approach can solve the problem, but it makes the code a little hard to understand for others.

That's why I am requesting such a feature. I hope that I've made myself clear.

[georgyfarniev]

Why vue-cli uses nightwatch instead of puppeteer? For running against multiple browsers?

[LinusBorg]

Exactly.

If you want to run against chrome only, we offer Cypress.

If you prefer puppeteer, write a plugin for it :)

[CommanderXL]

Is there any possible to add a hook for developers to modify the README.md?

In most situations, we use vue-cli to create some projects with default README.md generated by the readme.md utility function.So we want to generate the README.md file with different content after a project created by vue-cli.

[bodograumann]

Cf. #3547 @CommanderXL

[CommanderXL]

@bodograumann Well, I have seen that issue.So will it come to the vue-cli of v4? Or need us to do some pull request to accomplish this function?

[LinusBorg]

it's now marked as "contribution welcome" so we would be happy to see a PR for this.

[georgyfarniev]

Hello folks, I see that vue-next uses rollup for build, so is there any plan to support it as alternative to webpack in vue-cli?

[LinusBorg]

No. Supporting two build tools will increase complexity too much.

[georgyfarniev]

No. Supporting two build tools will increase complexity too much.

Agreed, thanks. So it will be used only for vue due to its simplicity

[haoqunjiang]

Released 🎉
The release note: https://github.com/vuejs/vue-cli/releases/tag/v4.0.0
The migration guide: https://cli.vuejs.org/migrating-from-v3/