esbuild VS Tailwind CSS

I recommend using NodeJS, not because it fits the event-driven, non-blocking model, but because it is very well-suited for reducing file size by bundling the code. Esbuild is a great tool to bundle your Lambda. It is already included in the CDK construct NodeJSFunction when using AWS CDK, and you don't need source maps, at least not in production.

You will find an issue related to pureannotations in esbuild repository.

Vite (pronounced veet) was created by Evan You (Vue's creator) and launched in 2020. It uses native ES modules in the browser and esbuild for lightning-fast dev servers and Rollup for optimized production builds.

Pre-bundle all the dependencies on the "optimization boundary" list into node_modules/.vite/deps/ folder. This step is done by esbuild.

ESBuild is a bundler. The subtitle on the website is literally “An extremely fast bundler for the web”. To bundle, pass —-bundle flag.

https://esbuild.github.io/

esbuild for bunding both the client and server separately

TailwindCSS

> When I’m trying to debug a web app, it’s hard to orient myself in the DevTools if the entire UI is “div soup”

That’s tame. Try adding some Tailwind CSS.

After monitoring Tailwind CSS since its early days, and believing I had some pretty serious philosophical disagreements with it, I recently took an opportunity to try it out in earnest, and it is so mindbogglingly obnoxious in dev tools that I think surely I must be missing something. How do people cope with this stuff!?

If you’re not sure what I’m on about, go through some of the sites linked near the bottom of https://tailwindcss.com/. In the Inspector/Elements panel, the DOM tree is a bloated mess with a class attribute which amounts to inline styles or worse, commonly hundreds of characters long, discouraging you from using semantically-meaningful classes, and duplicating stuff enormously rather than using sane selectors; the mostly-better ones are those that have data-sentry-{element,component,source-file} attributes. The styles subpanel becomes utterly unnavigable.

(I’m not saying everything in Tailwind is bad; I think I am likely to use a limited utility styles approach more than I did in the past, and there are a couple of other things that are provoking thought in me, and I think it would be more suitable in apps than in marketing-style websites. But the total embodiment of it is not for me.)

We use dynamic importing to solve a strange bug in Tailwind CSS that is marked as solved but still occurs.

UI: Preact + Tailwind/shadcn

Styling: Tailwind CSS (Assumed, common with Next.js)

This article assumes the reader is a developer that knows their way around Markdown, TypeScript, React.js, and [Next.js] https://nextjs.org/). Familiarity with Tailwind-css would also be useful.

Then I learned Tauri and used my favourite frontend framework SolidJS with TailwindCSS and DaisyUI to build the UI with MotionOne to add animations and Tauri to build the desktop/web/android/ios app.