stwui VS DivMagic

Check out STWUI for an alternative svelte tailwind component library. 50+ components and utilities. https://stwui.vercel.app/

Give STWUI a look https://github.com/N00nDay/stwui

https://stwui.vercel.app/ STWUI - TailwindCSS component library/design system.

https://github.com/N00nDay/stwui/releases/tag/v0.0.34-next

Or check out the repo on Github: https://github.com/N00nDay/stwui

I'm currently working on an extension as well ([0]) and share the same concerns many have mentioned about extensions here. I'd like to highlight another dimension concerning the Browser APIs ([1]).

Handling the permissions necessary for certain API functionalities and the corresponding warning messages can be somewhat confusing. For instance, our extension uses "chrome.devtools.panels" to open a new window within DevTools. This API doesn't require any permissions by itself. Yet, for messaging across the popup, content, and DevTools windows, we're required to use activeTab and sendMessage APIs. The DevTools window operates in its unique context, almost like a tab within another tab. For example, updating the URL in the active tab doesn't directly update the DevTools window but triggers an event.

Messaging across these different contexts requires the "https://*/*" host permission, without which Chrome and Firefox won't send the messages between these isolated windows.

We made this permission optional, the DevTools Panel is activated only upon receiving explicit user consent. However, the permission prompt's messaging is something like "This extension requires access to all your data," which sounds very alarming. We don't access any data nor that we want to, but requiring that permission is mandatory since the message APIs won't work without them.

This is just one example of the many undocumented complexities within Chrome's documentation. Similar pitfalls exist with message exchanges between the background service and content scripts. Sometimes you don't know why your API call doesn't work even though you think you have the required permission and asking for more permissions show very alarming messages to users.

I think that a more granular permission approach, made specific to API functionalities rather than broad permissions that cover a list of APIs, would significantly help user experience. For example, requesting permission for the "sendMessage API" with a clear explanation would be far more informative for users than the general "All host https:///" permissions.

There's also the issue of building for different browser. The same browser API calls can have different permissions requirement on Chrome and Firefox which makes the development process more difficult and more confusing for users since the same extension requires different permissions on different browsers.

[0] https://divmagic.com

You can see more demo videos here: https://divmagic.com

It doesn't need to be designed with Tailwind, just use DivMagic and convert it to Tailwind!

This is really Tailwind before Tailwind. I didn't know about it.

I'm working on a css style copying project on the side (DivMagic https://divmagic.com/) and I might add Tachyons as an option there

You can use DivMagic (https://divmagic.com)

I created a tool (DivMagic) which lets you copy any element from any website and convert it into HTML/JSX(React)/CSS/Tailwind CSS component.

You can make use of a tool like DivMagic (https://divmagic.com) to convert elements into inline CSS components

Wanted to shamelessly plug my tool here: DivMagic (https://divmagic.com)

I’m a big fan of Tailwind. I’d encourage you to checkout a tool called DivMagic. It allows you to copy any element from any website and paste them as tailwind components in your codebase. Super useful for building front ends quickly. Feels like a cheat code.

If none of the provided solutions work any you need to convert Tailwind CSS to inline raw CSS, you can make use of a tool like DivMagic (https://divmagic.com) to handle the conversion easily