Releases: kaliop/gulp-assets-builder
Releases · kaliop/gulp-assets-builder
5.0.0 — Update to gulp@4, gulp-task-maker@2
4.1.0
4.0.0
Rewrite on top of https://www.npmjs.com/package/gulp-task-maker
3.0.2
Fix an issue where this config resulted in a single task instead of two:
{
sass: {
// base settings
dest: 'public/css',
browsers: ['last 3 versions', 'ie >= 11'],
// builds with specific settings
0: { src: 'assets/styles/main.scss', watch: 'assets/styles/**/*.scss' },
1: { src: 'assets/styles/other.scss', outputStyle: 'compact' }
}
}
3.0.1
3.0.0
BREAKING CHANGES:
- Task dependencies are no longer in the
package.json
by default. On firstnpm run build
, any configured task with missing dependency will print information about the missing tasks, showing the command to install those. This makes it possible to have many task scripts inassets-builder/tasks
, without incurring a penalty for the tasks you don’t use. node-notifier
is not installed by default, but will be used if it can be required.
New features:
- Automatically list missing dependencies (using a
assets-builder/tasks/taskname.json
file as information source). - Ignore any config block by adding an underscore at the start of the config name.
less
task (LESS + Autoprefixer).sass
andless
tasks can optionally concatenate their results (using adest
config key ending in.css
).
2.0.0
BREAKING CHANGES:
- Renamed
gulp
dir toassets-builder
- Config now goes in
gulpfile.js
by default - The
assets-builder
module must be imported and called with the config object (seegulpfile.js
for a working example)
Previously, the package.json
scripts were set to use gulp/index.js
as a gulpfile, and that script would automagically load the config from a separate file (based on a package.json
config key). That was a bit too implicit, hence the new behavior.
Other changes include usability tweaks in logging and notifications.
1.2.0
- simplify config for multiple builds
jsconcat
task: opt out of minification withminify:false
Multiple build syntax:
{
taskname: [
{ build1… },
{ build2… }
]
}
or:
{
taskname: {
commonOption: 'value',
0: { build1… },
1: { build2… }
]
}
Previous release (1.1.0) used a builds
key instead of arrays/numeric keys.
Enable multiple builds per task
1.1.0 doc(readme): improve doc for svg task, sass task, multiple builds
Yay gulp goodness yay
1.0.0 Looks stable and stuff