3
4 Comments

Would you like to use a TailwindUI CLI?

Hey all,

I was thinking of building a npm package that helps build tailwindui components easily.

For example, if you need to init a react project you could use:

$ npx tailwind init projectname --react

this would initialize a boilerplate project including the tailwindUI components.

Also, you could build the pages by using:

import {  Navbar, Hero,  Features } from 'tailwindui'

const App = () => (
<>
<Navbar logo="Logo" links={['Login', 'Signup']} />
<Hero title="Awesome page heading" description="" />
...
</>
)

A lot could be achieved via this approach, but I wanted to validate if users would find this useful or not. What do you think?

on June 10, 2020
  1. 1

    Is this similar to what Adam announced yesterday?

    We're going to provide production-ready JS versions of each component in the coming months! 🥳

    We're working on a set of low-level renderless components that will make it much easier to build things like these custom select menus, without needing to be an expert in all of the accessibility stuff to make them work.

    We're going to start with Vue, React, and Alpine, with plans to add other frameworks in the future. The underlying libraries we are developing are going to be completely free and open-source, so you'll be able to use them on any project you want, even if you're not using Tailwind or Tailwind UI.

    Also, I think you need to be careful about the TailwindUI license here.

    You cannot:

    • Use the Components to create End Products that are designed to allow an End User to build their own End Products using the Components or derivatives of the Components.
    • Re-distribute the Components or derivatives of the Components separately from an End Product.
    • Share your access to the Components with any other individuals

    From the TailwindUI license agreement

    1. 1

      yeah. I had this plan for a long time now. I was initially thinking of distributing only the free tailwindUI components with permission from Adam.

      In addition, I was thinking of providing the library to the TailwindUI team to include the paid tailwindUI components to its members..

      But the question is: Would you love using it?

      1. 1

        I personally wouldn't use it, because I only want to make components out of the elements I'm actually going to use. The rest would feel like clutter to me.

        1. 1

          just skip the boilerplate - you can still use import { Hero } from 'tailwindui' to import only the elements that you're gon use