Basically, the same thing than that: https://tailwindcss.com/docs/max-width/#app

But for height.

I might add it on a tailwindcss config file, but I'm working on an open-source svelte library based on Tailwind, and I would keep the strict default config to be flexible.

This will be useful to set the max height of a dropdown. Currently, I have to do this:

.list {
  max-height: 1

I hate regex too and would rather not use it but my coworker do and it makes code review very hard.

I wonder if there could be a simple way to use your awesome service to improve code review.

My first idea was to document code with a link to your service identifying uniquely the regex in the code.

What do you think about it?

The various popup shown can be placed outside the viewport, making them hard to view/use.

For example, a tooltip can be partially hidden if the activator is in the right of the screen, or a menu can be longer than the viewport height.

Smelte should probably provides utils to position popup on the viewport.

(by the way, thanks for your work, smelte is great :)

Expected Behavior

Create a tutorial: how to install Awes.io without pkgkit.

Current Behavior

PackageKit is an optional service for the fast delivery of the applications. BUT for the testing and else we have to show how users can use Awes.io without PackageKit.

System GA

Thanks for the awesome plugin! ⚡️

The npx tailwind init is optional if you read the Tailwind CSS docs. It is a bit confusing if you skip that step, install the Tailwind CSS IntelliSense plugin, and autocomplete does not work.

In other words, it took me some time to figure this out. 😅 It would be great to mention this somewhere in the docs, so that other people would not waste time on this

Issue

Create-React-App has a plugin, ModuleScopePlugin, that stops components from accessing files outside /src/. Apparently, when I import tailwind in a component while using a tailwind.config.js in the root of my project, Tailwind can't access it, and I get this error:

./src/App.js
Module not found: You attempted to import ./../tailwind.config.js which falls outside of 

Thanks for the starter, using it as an intro to gridsome and tailwind. Quick question, any suggestions on how to incorporate multiple content types into a single search? For example:

const { collection } = store.getContentType('Post', 'Documentation');

But then there would have to be I guess some more complex joining after that... it's all new to me so if there's an easy way to do this I'd

Instead of

//..
  .opacityVariant('muted', .35)
  .opacityVariant('pale', .50)

Be able to do

//..
  .opacityVariants({
    muted: .35,
    pale: .50
  })