Releases: maizzle/framework
v4.4.1
Fixed
- fixed an issue where utilities in Templates inside directories with dots in their name (like
src/templates/test.com) were not being generated
Changed
- add
{raw: html, extension: 'html'}to Tailwind'scontent.filesonly ifhtmlwas passed to the Tailwind compiler - this happens/is needed only when using Maizzle programmatically, so we removed it for normal use cases
v4.4.0
🥳 v4.4.0 is here, bringing a new Components system, new Starter components, omit/skip, and tons of bugfixes!
New features
-
Blade-like Components system
We have a new, awesome Components system! It uses Blade-like syntax and comes with a lot of cool features, like slots, stacks, props, and more! Checkout the new Components documentation for more information.
-
Added new Starter Components: Spacer, Divider, Button
-
Added
shorthandCSSas an alias forshorthandInlineCSS#855 -
Added support for
config.cjsfiles #873 -
Added support for
fortag name in loops #902
Changed
- Updated the official Starter to use the new Components syntax
- Updated
tailwind.config.jsin the Starter to use types, so you now get autocompletion for config keys in your IDE - Improved build error message when you don't have a
build.templates.sourcedefined in the config #878 - Do not duplicate CSS properties to HTML attributes by default 6c36024
Fixed
- Fixed issue in
removeUnusedCSSwhere some selectors were being purged even if they were a pseudo selector or part of a media query #853 - Fixed an issue with removing possibly inlined CSS selectors from the
<style>tag #855 - Fixed an issue with CSS shorthand inconsistencies between inline CSS and CSS in
<style>tag #855 - Fixed an issue where the string
undefinedwas being prepended to VML src paths if you were using object syntax forbaseURL#857 - Fixed an issue with
baseURLdefaults preventing URLs from being prepended, when it was configured as an object #877 - Fixed an issue where new data added to the config while the server is running were not always available when developing locally #886
- Fixed a bug where your custom Tailwind config object was not being used when rendering emails through the Maizzle API #890
- Fixed an issue where information about the current template was not being updated when developing locally #897
- Fixed an issue where an empty Tailwind CSS config was being used when developing locally #899, #900
- Fixed an issue where saving a template file while developing locally was outputting it in a wrong location #901
- Fixed an issue where
removeUnusedCSSwas running in local dev, even though it wasn't enabled in the config f105672 - Fixed an issue with Tailwind CSS
contentpaths for Layouts and Components were removed if the user configuredcontentas an array in theirtailwind.config.js0641846 - Fixed specificity issue where you couldn't override an existing class because everything had
!importantd4e54da - Fixed an issue with the
permalinkFront Matter option not working 4e4f742
v4.4.0-beta.14
v4.4.0-beta.13
- fix: ensure
removeUnusedCSSis opt in f105672
v4.4.0-beta.12
- added support for self-closing component tags, so you can do
<slot:template />instead of<slot:template></slot:template> - prevent duplicating any CSS props as HTML attributes
- updated some dependencies
v4.4.0-beta.11
- feat: add
foras an alternative loop tag name 9d9d964 - updated dependencies
v4.4.0-beta.10
v4.4.0-beta.9
v4.4.0-beta.8
This release fixes an issue with the Tailwind CSS generator where your custom Tailwind config was not being used when passed to the render API method of Maizzle (#890).
v4.4.0-beta.7
This release fixes an issue where new config items added while developing locally were not available to templates (#885).