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
lateston 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-coredoesn't exist as a peer dependency,vueifywill not attempt to transpile content inside<script>tags in Vue components (they are treated as plain ES5). To makevueifyES2015-aware, simply install and configure Babel and other babel related packages as you normally would.vueifywill automatically detect their presence and apply babel transformation to Vue components. (You will likely needbabelifyfor normal*.jsfiles). -
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. Sincevueifyalready supports using PostCSS plugins, simply installautoprefixerand pass it tovueifyas 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
cssnanofield invue.config.js. Options are available at http://cssnano.co/options/
v7.0.0
- Added relative
@importpath support and import dependency tracking for LESS, SASS & Stylus. Now you can@importfiles 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.