prettier-plugin-tailwindcss VS node-sass

Since this was a problem that many people had already encountered, there was already a solution. The first thing I found was Tailwind's official Prettier plugin, which ensures that class names are always ordered according to a certain rule. Best of all, it's auto-correcting, so I don't accidentally miss something or commit a different order.

It's not as if the correct order for the rules is mysterious. It's implemented in the Tailwind compiler. Tools like prettier-plugin-tailwindcss, which automatically sorts the class names in your HTML code to match the order in which Tailwind generates them in your CSS output, use a public API in Tailwind to get this order.

Other than that, you can get Prettier sorting your classes with the Tailwind Prettier plugin. And one more quality-of-life extension that might help your eye sores from a long list of classes is Tailwind Fold.

I everyone. I am using Electron react boilerplate and I have successfully added tailwindcss to the project. However, I am struggling to get the Prettier plugin tailwindcss to work. I’ve tried following the instructions in the readme but no luck. I’ve tried moving my prettier.config.js to the .erc/config dir with no luck either.

Others have already replied, but if you need to structure your TailwindCSS classes, I recommend their official Prettier plugin which integrates well into an ESLint setup.

> Except that I read that it's great for writing, but a nightmare for reading.

This is true at first. I can see it being pretty daunting to come into an existing project and trying to understand the styling of components. Starting from scratch and easing it into an existing project is much easier imo. That's what I did for a personal website. Now that I understand it and have converted the entire website to Tailwind, I don't want to switch to anything else going forward.

Here's a Prettier plugin that sort the classes to keep everything consistent across components: https://github.com/tailwindlabs/prettier-plugin-tailwindcss

Tailwind combined with classnames (https://github.com/JedWatson/classnames) makes it really easy to have conditional styling based on component state.

Despite the existence of Prettier, arguments about code style such as how to sort ES module imports still exist. Manually sorting ES modules wastes time, and usually leads to losing context when you are writing code and then have to navigate to the top of a file to modify your import statements. I love using the @trivago/prettier-plugin-sort-imports plugin which automatically sorts new imports, and works perfectly together with TypeScript's auto-import feature. Similarly, prettier-plugin-tailwindcss automatically sorts Tailwind classes in your code.

Added the tailwind-prettier-plugin as not everyone uses headwind

For many years, Culture Amp took the second option, and distributed shared components without compiled CSS. This meant that every app that consumed shared components needed to include the necessary CSS build tooling – at that time CSS Modules and node-sass – with a compatible version and configuration. This was relatively easy to set up, but over time proved difficult to maintain. When node-sass was deprecated in favour of (the much faster but slightly incompatible) Dart Sass, this demanded a difficult lock-step migration across all those codebases, which we have yet to achieve. And as new applications have switched to Tailwind for their own styles, they've had to continue to maintain those old build tools in parallel for the shared components' styles.

The project that we developed use a node version 14.18.0 and we use a node-sass version 4.14.1 package and this package also deprecated for today.

ES 2 component Sass files are compiled using dart Sass instead of node-sass. This change was made because node-sass has been deprecated.

node-sass - yes i am aware its deprecated 😅

C:\Webparts\react-script-editor>npm install npm WARN deprecated @types/[email protected]: This is a stub types definition. classnames provides its own type definitions, so you do not need this installed. > [email protected] install C:\Webparts\react-script-editor\node_modules\node-sass > node scripts/install.js Downloading binary from https://github.com/sass/node-sass/releases/download/v4.12.0/win32-x64-83_binding.node Cannot download "https://github.com/sass/node-sass/releases/download/v4.12.0/win32-x64-83_binding.node": HTTP error 404 Not Found

Are you referring to when it's trying to download 'https://github.com/sass/node-sass/releases/download/v4.12.0/win32-x64-83_binding.node' after I typed 'npm install'?

This Github issue helped me a lot.

remote: ERROR in ./app/javascript/stylesheets/application.scss (./node_modules/css-loader/dist/cjs.js??ref--7-1!./node_modules/postcss-loader/src??ref--7-2!./node_modules/sass-loader/dist/cjs.js??ref--7-3!./app/javascript/stylesheets/application.scss) remote: Module build failed (from ./node_modules/sass-loader/dist/cjs.js): remote: Error: Node Sass does not yet support your current environment: Linux 64-bit with Unsupported runtime (93) remote: For more information on which environments are supported please see: remote: https://github.com/sass/node-sass/releases/tag/v4.14.1 remote: at module.exports (/tmp/build_37040035/node_modules/node-sass/lib/binding.js:13:13) remote: at Object. (/tmp/build_37040035/node_modules/node-sass/lib/index.js:14:35) remote: at Module._compile (node:internal/modules/cjs/loader:1101:14) remote: at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10) remote: at Module.load (node:internal/modules/cjs/loader:981:32) remote: at Function.Module._load (node:internal/modules/cjs/loader:822:12) remote: at Module.require (node:internal/modules/cjs/loader:1005:19) remote: at require (node:internal/modules/cjs/helpers:102:18) remote: at getDefaultSassImpl (/tmp/build_37040035/node_modules/sass-loader/dist/index.js:198:10) remote: at Object.loader (/tmp/build_37040035/node_modules/sass-loader/dist/index.js:80:29)

Ah damn I did not save the full error before uninstalling everything and rethinking my next move. From the various posts it seems I'm not the only one having the same issue, but never really found out what the smartest solution would be to go forward as none of those suggestions worked with the latest node-js version.