Update to latest Vue CLI v2 template #296
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As discussed with @chrismayer by mail a few months ago, I tried to upgrade Wegue to newer versions of Vue-CLI and Webpack (just to mention those two). See #94.
This project was going well until the end of April when I unfortunately had no more time to work on this. Here I had a little time again and managed to get almost to the end of it. So I think it's time to share...
I'll make a serie of PR, each going to the latest template used by the next Vue-CLI version.
For this one, nothing really big, it's just going to the latest template of Vue CLI V2. The major improvements are linked to a fully functional ESLint and an upgrade from Webpack 2.7 to Webpack 3.6.
This is also using Webpack-dev-server instead of running Express directly.
There is a bug here though in this version of the dev-server (which will be resolved in next PR with Vue-CLI V3) where compilation warnings issued while in dev mode are all reported as errors. So you can have the browser overlay report everything as errors or hide it completely (which I have done here). You can easily put it back on by going in the build/webpack.dev.conf.js file and change the overlay parameter, setting warnings to true instead of false.
I hope to post a PR for Vue V3 this afternoon, V4 should follow shortly and I still have to work a little bit on V5.
If you have ideas or requests to configure some things differently, don't hesitate to ask, I'll try to add what I can in coming PRs.