typescript-book VS Tailwind CSS

This looks the same as a barrel import.

This is a great overview of some deep parts of TS

https://github.com/basarat/typescript-book

typescript-book 📚 The definitive guide to TypeScript and possibly the best TypeScript book 📖. Free and Open Source 🌹

The first time I encountered the concept of “Type flowing” was in PranshuKhandal’s TypeScript book. He explains this idea in the following way:

In addition to Airbnb's ESLint config, I find basarat's TypeScript styleguide very useful.

index.ts is just for ease of use. It imports everything inside api/graphql folder and re-exports it like a barrel. It acts as a simple aggregator of the other files to make imports easier down the road.

A good starting point for beginners is the "TypeScript Deep Dive" book from Basarat Ali Syed. It's free and has a "Getting Started" section for beginners. I recommend you to start from there and to look up advanced chapters as you progress.

Lastly, Tailwind CSS is a utility-first CSS framework packed with classes like flex, pt-4, text-center, and rotate-90 that can be composed to build any design, directly in your markup.

Tailwind CSS

Sidekiq is already configured along with assets, tailwindsCSS.

Finally, for our front end, we’re going to be pairing Next.js with the great combination of TailwindCSS and shadcn/ui so we can focus on building the functionality of the app and let them handle making it look awesome!

You can use any frontend framework you want — react-based tooling, however, has a natural advantage as it models everything as a function of state, which can map 1:1 with the concept in Burr. In the demo app we use react, react-query, and tailwind, but we’ll be skipping over this largely (it is not central to the purpose of the post).

Tailwind CSS: A utility-first CSS framework for rapidly building custom designs.

First, you need to make sure that you have a working Tailwind CSS project…

Tailwind CSS

With better CSS approaches like TailwindCSS and Vanilla Extract (which we're heavily using) it's much easier to maintain the UI and make sure it doesn't change unexpectedly. No more conflicting CSS classes, much less CSS specificity issues and much less CSS code in general.