ReactTemplate VS classnames

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.

The component needs the classname dependency and a search icon which I referenced to work. So install the classname package and download the search icon below.

classnames: Makes dynamic CSS class application a breeze. Learn more

But of course, it is a button, so it could have multiple variants: primary and secondary(you can increase the number of customizable params, but we will limit it to 1, variant). To implement this you can use any library for combining classnames, for example, classnames, clsx. Let’s use the classic one, "classnames".

Use classnames and you can comma delimited your class names where needed.

To get started with our image modal implementation, i'll assume you already have a React project set up. For UI i’m using Tailwind CSS. But you can use any UI library as your wish. For the image cropping and rotating functionality, we'll be utilizing the react-easy-crop library. This library provides a simple and intuitive way to crop and interact with images and videos within a React component. We will also use the heroicons and classnames libraries in our tutorial. To install all the libraries and their dependencies, open your terminal and navigate to your project's directory. Run the following command:

Save yourself some headache and use https://github.com/JedWatson/classnames

There is an NPM module called classnames that makes this a bit easier: https://www.npmjs.com/package/classnames

To use the global Tailwind types from styles/cssClasses.d.ts, I've leveraged a lot of work from this post, so credit goes there for a lot of the complex TypeScript wizardry that makes things work. In essence, it builds upon the classnames (or clsx) to provide a helper function that gives us with the type safety we're after. This cleverness means we get type checking that works with whitespace, multiple classes (e.g., "container p-5")and arbitrary values (e.g., "border-[5px]"). The input "container p-5 invalid-class" provides the nifty error message:

but I wouldn't recommend it, because I think the point of using tailwind is to not having to abstract class into component based style. it even better to write tailwind classes into the html directly and to use tailwind-fun sparingly and only if you needed to add logic to your classes. tailwind-fun purpose is more like of https://www.npmjs.com/package/classnames rather than any other css library

Use the classnames library, that way I can group the utility classes together (one line) and break them up into multiple lines, and additionally have some of them be conditional based on variables/parameters;