Releases: maizzle/framework
v1.1.0
First feature release since v1.0 🎉
Multiple asset paths
You can now define multiple asset paths, with an array. For example:
// config.js
module.exports = {
build: {
assets: {
source: ['src/assets/images', 'src/fonts'],
destination: 'assets',
},
// ...
}
}Disable safeClassNames
You can now disable the safeClassNames transformer:
// config.js
module.exports = {
safeClassNames: false,
}Doing this will no longer replace escaped characters in CSS class names with email-safe alternatives.
Updated extraAttributes
extraAttributes now uses PostHTML too, replacing cheerio. This was done so that we push the HTML through a single parser, for consistency and predictability - except the inliner, all transformers in Maizzle now use PostHTML.
See docs for new extraAttributes options.
Bug Fixes
Fixed an obscure issue with posthtml-safe-class-names, where CSS comments containing HTML tag names were breaking the build (posthtml/posthtml-safe-class-names@3d7deb9).
See full diff:
v1.0.9
This release updates some dependencies and fixes issues with ignoring expression delimiters (#160 and #171).
- build: update dependencies 828e397
- build(deps): bump front-matter from 3.1.0 to 3.2.1 21ba57a
- build(deps): bump email-comb from 3.9.14 to 3.9.16 21935ea
- build(deps): bump string-strip-html from 4.4.3 to 4.4.5 c6249a3
- build(deps): bump postcss from 7.0.29 to 7.0.30 7bd7f37
- build(deps): bump posthtml-expressions from 1.4.0 to 1.4.1 737b0ec
- build(deps): bump html-crush from 1.9.31 to 1.9.33 a0ec0cd
v1.0.8
- test: add tests for helpers d0b1281
- test(tostring): add inheritance test 0792e13
- fix(posthtml): use expressions plugin last 211d64e
- revert(posthtml): remove initial option from modules plugin 9a2abc8
- fix(tailwind): prepend passed css string to css from existing file aad35d1
- build: disable complexity in linter 878cefc
- refactor(tailwind): use a single function for css compilation 9c329cd
- test(transformers): update transform test 16d43c1
Full diff: v1.0.7...v1.0.8
v1.0.7
This release bumps some dependencies versions, and fixes an issue with safe class names not working with @font-face.
- chore: bump posthtml-safe-class-names 8f40131
- build(deps): bump postcss from 7.0.28 to 7.0.29 1446d9a
- build(deps): bump posthtml-mso from 1.0.0 to 1.0.1 cd5dad2
- build(deps): bump tailwindcss from 1.4.0 to 1.4.4 4ddd93c
- build(deps): bump postcss from 7.0.27 to 7.0.28 90518bb
- build(deps-dev): bump np from 6.2.2 to 6.2.3 e92835a
v1.0.6
v1.0.5
v1.0.4
v1.0.3
v1.0.2
This release adds support for Tailwind 1.4
target
In order to ensure email-compatible background-color and color utilities, this release uses target: 'ie11' by default behind the scenes. However, you are free to override it in your tailwind.config.js.
CSS purging
You can use Maizzle's purgeCSS config options, the purge config key from Tailwind, or even a combination of the two. Content sources, as well as PurgeCSS options are collected by Maizzle from both places and merged into a single config object that it uses to purge unused CSS.
This will always run only once, so you don't need to worry about it running twice just because you prefer using Tailwind's config for the PurgeCSS options 👍