Unfortunately, package.json currently allows updates to ^3.1.6 (semver compatible to 3.1.6) which includes 3.3.x, so (as long as this isn't properly fixed) intermediate releases with pinned tailwindcss < 3.3 could be a quick fix. Otherwise users of the library can just locally pin tailwindcss to e.g. 3.2.7.
Tailwind 3.3.0 introduced new
from-x%
|to-x%
|via-x%
utility classes which break the generated elm code in both elm-tailwind-modules 0.4.1 and 0.5.0-alpha5.The invalid generated elm code looks like this:
Unfortunately,
package.json
currently allows updates to^3.1.6
(semver compatible to 3.1.6) which includes 3.3.x, so (as long as this isn't properly fixed) intermediate releases with pinned tailwindcss < 3.3 could be a quick fix. Otherwise users of the library can just locally pin tailwindcss to e.g.3.2.7
.