Max Barvian

Hey, thanks for filing. The warning is there because that text wouldn't enlarge to 2x its size if someone tried to 5x zoom the page at a screen width of...

@kobe-f8 @peterpalkovic I'm thinking of adding an option you could pass to the plugin that would warn about these issues on the console but still output the fluid code. Would...

@krstivoja Working on this feature for v0.2.0! Here's a [preview of the docs](https://fluid-tailwind-git-v020-barvians-projects.vercel.app/?_vercel_share=Cq44ksS5u2s4nrlgddt1uMV3IEc5YP9a#fluid-type-accessibility-errors)

This feature is now live in v0.2.0 (see #15)! Feel free to comment in the discussion or open another issue if you find a bug. Thanks for the feedback 🙂

Hey @peterpalkovic, unfortunately I think you'd need two sets of breakpoints at the moment, one in `rem`s and the other in `px`, i.e.: ```js // tailwind.config.ts screens: { sm: '30rem',...

Hmm, it looks like a regression in the last update. Could you try `https://esm.sh/[email protected]?bundle-deps&external=fs` for now? I'll look into the cause and try to push a fix in the meantime...

I've opened [an issue](https://github.com/esm-dev/esm.sh/issues/826) with ESM.sh because I can't seem to find what changed between versions to cause this breakage 🤔

This should be fixed with v0.3.6. Here's [a working StackBlitz](https://stackblitz.com/edit/stackblitz-starters-wxvznu?file=index.html) that should be adaptable to Winden/Yabe Suil. Note the (currently undocumented) option passed to the plugin: ``` plugins: [ fluid({...

Hey, thanks for the write-up. I thought about adding this a while back but I decided against it for a few reasons: 1. It feels a little out of scope....

Hey, thanks for the big write-up! I definitely hear the concerns about the extractor being incompatible with presets. I like the idea of utility functions and I think I may...