Releases: vuejs-templates/webpack
1.3.1 [Bugfix] - Node 6 compatibility
Things we fixed
1.3.0 - Introducing eslint-plugin-vue
About this Release
eslint-plugin-vue was officially released on Janaury 1st, 2017.
this release will add this plugin by default with a couple of sensible but rather unobstrusive rules. Be sure to check out the docs in the plugin's repo to learn about all the goodness you can bring to your Vue components with the other rules that are available, e.g. the "strongly recommended" rules.
What does that mean for the 'Standard' and 'Airbnb' styles?
In short: nothing. eslint-plugin-vue
does n't have any "code-style" rules about semi-colons or similar things. Rather, it enforces Vue-specific rules only and can happily live alongside either style.
Is some additional config required?
No, everything should just work.
Things we improved
No other improvements in this release despite some typos corrected.
Things we fixed
- When using a sbdirectory as
assetsPublicPath, historyFallback now works correctly again for windows systems as well
(42cd10c)
Internals
We completely switched the CI setup to test this repository (#1218), now using CircleCi v2 to test different installation scenarios in parallel. If you want to introduce a PR that adds a new option to the questionnaire during install, be sure to have a look at /scenarios
to learn how to set tihose up for the tests to pass.
v 1.2.8 - Maintenance
Things we improved
- webpack-dev-server now correctly serves files from
/static
even ifassetsPublicPath
has been changed. (#1180), thx to @nkovacs and @alxppp - We now use postcss-url to make relative files work correctly in imported .css files. (#1115)
- Some small typos in docs and files corrected
- babel-loader now also converts the client code of webpack-dev-server. Fixes #1140
Other changes
- This template now requires node
>=6
, so we're dropping suport for node 4, basically. Since vue-cli itself doesn't support node 4 anymore as well, that's a logical step.
Bugfixes...
Things we fixed
- AutoInstall now works reliably on Windows (#1170, @sudo-suhas)
- The Message after autoinstall was improved to better reflect the chosen options and show better commands for yarn (#1158)
webpack.base.conf.js
now doesn't contain useless code if eslint was not chosen during init. (#1165, @Toilal)
Housekeeping
- removed a dependecy we don't need anymore (#1169, @PanJiaChen)
- some code style cleanups (also in #1158)
...that's all!
Adding Autoinstall, JSX support, fixing a few minor things.
Thing we added
- Auto-install! You can now let the template install the dependencies for you right after the questionnaire:
This also runs npm run lint -- --fix
, so all project files are automatically formatted according to the eslint config you chose (if any). That means we as the maintainers have a far easier time handling boilerplate files like HelloWorld.vue
(since we don't have to accommodate the different eslint configs within those files), which means it will be easier and quicker to add new variations (e.g. typescript support, we'll see :) ).
- We now install
babel-plugin-transform-vue-jsx
and its peer dependencies by default, so JSX is not a first-class citizen for this template.
Things we improved
- the eslint config that is generated when choosing the Airbnb preset now comes with an adjusted rule that makes the preset play nice with Vuex state mutations. (#1003, @anubhav7495, adjusted by @LinusBorg with cc89353).
Things we fixed.
- Since babel-preset-env doesn't yet support
browserslist
in package.json until babel7 is released, we had to revert #1004, also added docs explaining this (1083, #144 thanks to @sudo-suhas) - CSS from codesplit .vue files is now also extracted into the main .css file. Previously, it was contained in the codesplit chunk and inserted at runtime via vue-style-loader. That unfortunately has some (not vue-related) problems with sourcemaps. (See discussion here: #1110), (PR: #1149)
v 1.2.5 - Polishing
Things we fixed
- When providing a port for the devserver with the PORT env variable, the value is now properly coerced to a number (#1099, 17a0e5c)
Things we improved
- Switched to the new version of the uglifyjs-webpack-plugin, which uses the latest uglifyjs so we can minify code that uses ES6 syntax (@sudo-suhas, #1119 ).
- dependencies in
package.json
are now properly sorted in alphabetic order (@jakub300, #1118) - We updated a couple of pages in the template docs in minor ways (d0b9007, #1092)
- the project url shown in the console after the devserver started now respects the
host
setting from/config
or a HOST env variable (@joltmode, #1103). - prevent webpack from inserting useless mocks (7cf7d41)
Maintenance
A Bunch of Fixes
Things we fixed
We mainly improved on the Jest integration which we introduced in v1.2.0
- Total overhaul of theconfig thanks to @Akryum (#1074)
- add support for async imports in jest ( #1075)
- made jest ignore any tests in
/test/e2e
to prevent accidental runs of *spec.js files meant for nightwatch (b14a70a)
Other
- It seems we forgot to actually pass the
cacheBusting
option we introduced to vue-loader (9f51df9) - When the new error notification is enabled, it no longer breaks the build process when the error doesn't provide a filename. (#1070, @wolfstark)
Things we improved
- webpack-dev-server now serves compressed assets, and some other small refactors (472c561)
Things we reverted / removed
- #997 actually leads to bigger file sizes in the bundled output, and bundle file names shouldn't be too important in production, so we reverted it (#86, @c0defre4k)
v1.2.3 - Small Improvement / Bufix
Things we changed
- We mistakenly had two instances of the
FriendlyErrorsPlugin
in the dev config, which resulted in all console messages from webpack being logged twice ( fixes #1064 )
v1.2.2: Bugfix release
Things we fixed
- The postcss improvement of the previous version was incomplete, and didn't work for
.css
files imported inside of.vue
files. This update addspostcss-import
to the postcss config, and with that, postcss is applied to all css. ( #1053 ) - The default config of webpack-dev-server is very noisy in your browser's console - every HMR action logs multiple lines. After @Frondor raised our awareness about this, we reduced the
clientLogLevel
option of the devServer to only log warnings and errors. ( #1063 )
Things we cleaned up
v1.2.1 - Bugfix release
Things we fixed
- Added postcss-loader, which was mistakenly removed by when merging #824
- set coverage directory for jest
- Fixing gammar in docs &
/config/index