-
- Maizzle Version: 4.6.1
- Node.js Version: 19.9.0
I get the following error when attempting to run the dev server on a fresh install of Maizzle:
```
✖ Error: Failed to find 'tailwindcss/compo…
-
For the case of `flox install nodePackages.@angular/cli` and many other nodePackages, as well as some `emacsPackages.@` pacakges, include the `@` in the package path. This conflicts with the flox co…
-
- Maizzle Version: 4.4.4
- Node.js Version: 16.15.0
I found that when using the transformer `removeUnusedCss` on very large files (several thousands lines of code in the build file), some unwanted…
-
- Maizzle Version: ^4.8.4
- Node.js Version:^18.17.0
- Svelte Version: ^5.0.0-next.143
Hi all,
Seems others have managed but not sure how best to get around issues with Browser-sync requiremen…
-
- Maizzle Version: 4.8.5
- Node.js Version: 18.18.2
If I am using my component props inside template to combine arbitrary class, like `max-w-[200px]` it not generates tailwind class for that :(
…
-
- Maizzle Version: 4.8.4
- Node.js Version: 18.19.0
Hello,
I find that the exit code will be set to zero even if there is an compilation failure across templates:
Log:
```
$ maizzle build …
-
Since our WYSIWYG editor is using tw's prose we can't use the traditional react.email, svelte-email, etc. Instead we have to programmatically generate our templated with maizzle because maizzle appare…
-
- @maizzle/framework: 4.4.4
- Node.js Version: 16.13.0
After running `maizzle build en --bin ../../../node_modules/@maizzle/framework/src`
```
✔ Built 2 templates in 0.229s
node:internal/mo…
-
As brought up in the conversation attached: Maizzle doesn't handle `@tailwindcss/typography` plugin well, and mostly produces invalid HTML/CSS.
Here's an example:
```
…
-
I've had no issues before but haven't updated in a while, being as we're still on `v4` I just wholesale updated from `4.0.2` to `4.4.4` and now `maizzle build --bin ....` breaks because `updateNotifie…