postcss-import VS Tailwind CSS

This might be your issue: https://github.com/postcss/postcss-import/issues/435

You can import custom CSS files from your application.tailwind.css file using postcss-import. After installing the package, you need to add it to your postcss.config.js, in the order specified in the docs. If you're using the Tailwind CLI for compilation (with cssbundling-rails you'd find this in your package.json), you might need to add the --postcss argument, which tells Tailwind to pick up your postcss.config.js.

postcss-import

postcss-import is used to replace @import with actual code.

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.

This app was built with Svelte Kit, Tailwind CSS, and many other technologies. For a full rundown, please visit the GitHub repository