ReactTemplate VS Alpine.js

I've never found CRA makes project management any easier (aside from the first few days after setting up a new project). In the long run it's always been a pain as it prevents you from touching most of the config. Personally I use this ReactTemplate which uses many of the same tools as CRA but with everything exposed and much more sensible defaults so it's easy to configure for whatever you want and nothing is forced upon you.

Most people have only ever used Webpack via CRA which is a terribly optimized config. If you design your own Webpack config it can be so fast that you won't notice it. (Example)

I recommend setting up tsconfig with strict mode enabled and ESLint and TypeScript ESLint rules to be fairly strict. This is a great way to learn with guard rails as it'll slap you when you try to do something which is unsafe or too loosely typed. Here's a reference ESLint config that is frequently updated with any newly released rules that fit well. This happens to be for a TypeScript React project, but you can always trim out the rules from plugins that aren't relevant for you.

Don't forget ESLint. Arguably more important than many of those other things for fixing the common mistakes that most developers make. And note that the recommended ESLint configs are incredibly conservative so you probably want to customize the rules to get much higher quality. An example of one of my recommended React/TypeScript ESLint configs.

And then I have a ton of code-level tools and configs that I use all the time. Many of which are in this React Template if you want to pick through it. There's code spellcheckers, dependency update checkers, extensive linting configs and more.

If you want a reference, take a look at this eslint config for some good rules to use.

If you want a reference, this ReactTemplate is very simple and in many cases can be used as a drop-in for CRA.

No reason to go overkill with a metaframework. All you need is a new build config. That's all CRA is, a collection of configuration files. I choose to just configure what I need myself so I have control over it and can easily customize it and get all of the features and performance that I want if I want it. The content of your app shouldn't need to change just because your build process changes. (If you want a reference, here's the React Template I start with.)

Yeah here's the config from my open source React Template: https://github.com/CreativeTechGuy/ReactTemplate/blob/main/.eslintrc.js

PS: If you are curious, this is my React Template that I was describing above.

Alpine.js for reactive frontend

✨ In recent months, I have been developing web projects using GOTTHA stack: Go + Templ + Tailwind CSS + htmx + Alpine.js. As soon as I'm ready to talk about all the subtleties and pitfalls, I'll post it on my social networks.

> But honestly, torn towards htmx but undecided.

We are in the middle of migrating from our monster react application into server rendered pages (with jinja2). The velocity at which we are able to ship and the reduction of complexity has been great so far.

Managing client side state for simple things like (is the dropdown open/closed), listening to keyboard events and such can be done with something like alpine-js [1] without all the baggage that something like react brings.

It appears this is already the trend with JS frameworks too - with server side rendering being the new norm.

[1] https://alpinejs.dev/

Sure, you can use any number of JS-avoidance libraries. I'm a fan of Turbo, and there's also htmx, Unpoly, Alpine, hyperscript, swup, barba.js, and probably others.

Direct DOM, but with a library. Specifically AlpineJS since it follows Vue closely in design practices allowing me to scale into a full web application if necessary (basically swapping to Vue takes minimal work). The Morph plugin is specifically what I like using.

If you want more details on the initial setup I encourage you to take a look at the Part I that covers more of the initial implementation. For this portion, I added Prisma as an ORM, a frontend style library called Tachyons, and AlpineJS to handle any client-side interactions. I did this to avoid needing to add a client-side bundler to the build and instead just rely on plain old module imports to compose the frontend. This is now the default for Rails and it is quite nice to not need any additional build tools for the client.

- [swallow-pywebview](https://github.com/rangwea/swallow-pywebview)： Base on [pywebview](https://pywebview.flowrl.com/) using Python，the frontend base on [alpinejs](https://alpinejs.dev/) and [tailwindcss](https://tailwindcss.com/)。

If you’ve followed our other tutorials, you might be familiar with Alpine.js. It’s a lightweight JavaScript library that allows you to add interactivity to your site without writing a single line of JavaScript. It’s incredibly easy to use, and we’ll show you how to make the animation trigger when the user scrolls to it.

The approach is not new, essentially a variation of Knockout, Alpine, and similar "JS-in-HTML" approaches.