Releases: vuejs/vueify
v9.4.0
New
- Support loading
vue.config.js
(@AdamNiederer via #146)
Fixed
- Fixed errors with scoped css (@danieldiekmeier via #154)
- Fixed CSS extraction plugin memory leak (@danieldiekmeier via #156)
- Fix Node async API deprecation warning (@mike-grinspan via #163)
v9.2.2
v9.2.1
v9.2.0
v9.1.0
v9.0.0
This release is not tagged as
latest
on npm. You will need to explicitly install it asvueify@next
.
New
- Supports Vue 2.0!
Breaking Changes
-
Does not work with Vue.js core 1.x, due to the different template compilation requirements.
-
Babel no longer required
If
babel-core
doesn't exist as a peer dependency,vueify
will not attempt to transpile content inside<script>
tags in Vue components (they are treated as plain ES5). To makevueify
ES2015-aware, simply install and configure Babel and other babel related packages as you normally would.vueify
will automatically detect their presence and apply babel transformation to Vue components. (You will likely needbabelify
for normal*.js
files). -
Removed CSS autoprefixing
This is not strictly within the scope of
vueify
, and in most cases you will need to configure it with targeted browsers anyway. Many PostCSS-based frameworks have this included as well. Sincevueify
already supports using PostCSS plugins, simply installautoprefixer
and pass it tovueify
as a PostCSS plugin invue.config.js
.
v8.4.0
v8.3.6
- CSS minification is now safe by default
- CSS minification options can now be configured via the
cssnano
field invue.config.js
. Options are available at http://cssnano.co/options/
v7.0.0
- Added relative
@import
path support and import dependency tracking for LESS, SASS & Stylus. Now you can@import
files using relative paths to the file being edited, and editing these imported files will also trigger watchify rebuild. - Removed built-in compiler for
myth
. Prefer using PostCSS + CSSNext.