The plugins in the official PostCSS website were old like IE6 or the marquee tag, and. - Source: dev.to / over 1 year ago
Hello internet. I just published a new blog post on how to implement dark mode with SvelteKit, optionally with PostCSS and TailwindCSS:. Source: 7 months ago
There are many frontend tools available for this purpose. For example, PostCSS is a popular CSS processor that can combine and minimize your code. With the right plugin, it can even fix your code for compatibility issues, making sure your CSS styles work for all browsers. - Source: dev.to / 7 months ago
I use PostCSS to extend CSS’s features and to add a few things that make writing styles a little more convenient, but it could easily be swapped for another preprocessor like Sass or vanilla CSS. It’s up to you. You can view my PostCSS config here. - Source: dev.to / 7 months ago
Code transpilation isn't specific to JavaScript, You can also add a level of transformation to your CSS source using tools like post-css. Most languages with a fairly mature ecosystem will probably have some tools to help with code transformation. - Source: dev.to / 9 months ago
In large projects, it is still a good idea to use PostCSS, which will translate new CSS features to something that browsers understand today. - Source: dev.to / 10 months ago
LiveCodes provides many of the commonly used developer tools. These include Monaco editor (that powers VS Code), Prettier, Emmet, Vim/Emacs modes, Babel, TypeScript, SCSS, Less, PostCSS, Jest and Testing Library, among others. All these tools run seamlessly in the browser without any installations or configurations. It feels like a very light-weight version of your own local development environment including the... - Source: dev.to / 10 months ago
Usually, one of the first things I do on creating a new web app is to throw a UI library in to help style components. There are several UI libraries that can be used by Svelte, but in this case I went with daisyUI because it's a fairly popular UI library which includes tailwind. To install daisyUI, you first need to install tailwind. There's a few different ways to do this (such as this guide), but the easiest... - Source: dev.to / about 1 year ago
Vanilla CSS has taken a similar path with ambitious working drafts, better browser support, and PostCSS to fill the gap for user agents lagging behind. So why is Sass/SCSS still so popular? Maybe we go so used to it that we might have forgotten what problems it was meant to solve in the first place. - Source: dev.to / over 1 year ago
Actually, Vite doesn’t support Browserslist at all: the only reason it “seems” to work well with CSS is because Vite uses PostCSS, which itself natively uses Browserslist. We could say that Vite supports Browserslist by proxy, for CSS. - Source: dev.to / over 1 year ago
But... This is still hacky! Can we do better? Yes, we can, using PostCSS to transform @when rules to the css we have seen above. I could not find any PostCSS plugin for this, so I created one that is really quick and dirty, but works for this simple use case. You can find it here. - Source: dev.to / over 1 year ago
Something like this https://postcss.org/. Source: over 1 year ago
Tooling takes away alot of headaches and saves yourself from "being clever" (stupid). Most front-end tooling can be run out of the nodeJS runtime, so even if your stack isn't JS oriented, it's still worth running node. The obvious shoutouts: Vite, eslint, stylelint, postCSS, browserslist. Playwright is somethin else you can give a look at if your scope of work is large enough. Source: over 1 year ago
As we write more features we would need to organize our css files, write additional styles or wrap any tailwind components up using tailwinds @apply helper. Currently, we can’t import other css files into the main application.tailwind.css file because our node-powered TailwindCSS is provided by cssbundling-rails, which by default doesn’t allow it. Luckily we can fix it, thanks to postcss. - Source: dev.to / over 1 year ago
There are few ways to add CSS library to our blog, because Hugo supports multiple ways to do asset management. If you used TailwindCSS before you may know that to better integrate with other build tools, like webpack, Vite etc., it supports PostCSS out of the box. Luckily for us, Hugo supports it as well. We are going to install TailwindCSS as a PostCSS plugin and then use Hugo's PostCSS pipe to integrate it to... - Source: dev.to / almost 2 years ago
The goal is to make your Ember.js app integrate with PostCSS and use Tailwind as a plugin. - Source: dev.to / almost 2 years ago
It really depends what you want to do for you. I’m gonna say, if you need total modularity and have a plug-and-play solution that works for any use case and can be as complex or simple as you want - PostCSS. It’s the bomb, since I’ve started to become familliar with it I threw SASS/LESS in the bin as 100% redundant, slow and unpractical garbage. Source: almost 2 years ago
The second of those two reasons is very disappointing, as PostCSS is a rich ecosystem of plugins to extend your CSS' functionality and build process. PostCSS is what Babel is for JavaScript, and unfortunately styled-components is missing out on an entire suite of new functionality. - Source: dev.to / about 2 years ago
Same goes for PostCSS, which I also mentioned. If you don't know what that is, please do take the time to find out. I suggested that you may want to avoid it for the time being while you're still learning, though. Source: about 2 years ago
PostCSS is a whole other package. Tailwind can integrate with PostCSS. Source: about 2 years ago
With the pre-processors, you can shrink your CSS and increase reuse through variables. In almost all working cases, it will be an improvement above vanilla CSS. There are also implementations now, via PostCSS, that add vendor prefixes for you. The major drawback is, of course, that you have to compile your CSS beforehand; usually done via part of your tooling such as Grunt or Gulp. - Source: dev.to / about 2 years ago
Do you know an article comparing PostCSS to other products?
Suggest a link to a post with product alternatives.
This is an informative page about PostCSS. You can review and discuss the product here. The primary details have not been verified within the last quarter, and they might be outdated. If you think we are missing something, please use the means on this page to comment or suggest changes. All reviews and comments are highly encouranged and appreciated as they help everyone in the community to make an informed choice. Please always be kind and objective when evaluating a product and sharing your opinion.