Releases: clay/claycli
Releases · clay/claycli
portable-templatization
- FEATURE: precompile templates for
npm
components (not just components in a single clay repo) - fixed issues when running
lint
/import
/export
outside of clay repos
tower-of-babel
- FEATURE: now uses
@babel/preset-env
instead of the oldbabel-preset-es2015
, allowing for more new javascript patterns - update babel dependencies to v7
- update vueify to use babel 7
fsevents
- include
fsevents
as an optional dependency sochokidar
will always use it when running on osx
vue-css
guilty-spark
- fixed v3.4.x
import
issues by explicitly formatting the input source for dispatches
Official Support:
stream of strings
- e.g. piping multiple files directly intoclay import
string
- e.g. piping a single file intoclay import
object
- e.g. programmatically callingimport()
with each result fromexport
methodsBuffer
- e.g. pipingclay export
intoclay import
yaml-handling
- fixed critical bug introduced in v3.4.0 (present in v3.4.1) that affects yaml handling
template-optimization
- fixed issue with template concatenation (gulp-if doesn't work well with gulp-group-concat)
- fixed issue with template incremental compilation (all source files check against dest file now)
- fixed issue with vue-template-compiler (pulling getDependencies out into a separate file)
Note: While you may still call getDependencies
from require('claycli').compile.scripts.getDependencies
, it is recommended that you instead require it directly via require('claycli/lib/cmd/compile/get-script-dependencies')
as this avoids some edge cases around a 3rd-party dependency of the script
compiler (namely, vue's template compilation script).
import-obj
- FEATURE: allow
import
to be passed a stream of objects, not just strings (useful for piping programmatic export to programmatic import) - use
@nymag.vueify
fork explicitly, rather than pointing at our github repo
parse-bootstraps
- FEATURE:
import.parseBootstrapObject
which can parse bootstraps that are streamed in as JSON
uglifyifyify
- explicitly require uglifyify because browserify's resolution wants to try and find it inside
<current working directory>/node_modules
rather than looking for it inclaycli
's folder