Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Maizzle 5 #1299

Open
wants to merge 180 commits into
base: master
Choose a base branch
from
Open

Maizzle 5 #1299

wants to merge 180 commits into from

Conversation

cossssmin
Copy link
Member

@cossssmin cossssmin commented Jul 18, 2024

The next version of Maizzle. WIP.

Maizzle 5 comes with awesome new features like:

  • New dev server with HMR*
  • 10x faster local dev
  • Streamlined configs
  • Streamlined Tailwind CSS usage
  • npx create-maizzle
  • Revamped CLI
  • Content source globs
  • Updated template
  • Better modern CSS support
  • Improved type definitions
  • New tags (<env:?>, <template>)
  • Enhanced events/hooks
  • ...

Maizzle 5 requires Node.js 18.20+

* Hot Markup Replacement™


Closes #1221
Closes #1328
Closes #1324
Closes #1323
Closes #1322
Closes #1321
Closes #1320

@cossssmin cossssmin changed the title Next Maizzle 5 Jul 18, 2024
get parser directives working again
no-widows is just shorter to write than prevent-widows
if content paths had just one extension, it would have always defaulted extensions to look for to 'html'; made it impossible to look for both html and md templates to compile, for example
support new project starter structure, with backwards compatibility
it's redundant, nothing that could be used in an event happens before `beforeRender`, so that can be used instead
defaults to true, resolves css variables to their static representation all the time, not just when inlining css
no longer needed if we resolve all vars by default
resolve calc() functions throughout CSS, not just in inlined styles
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment