PostCSS Reviews and details

Social recommendations and mentions

• How to setup a simple static website using Svelte (with login)

  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 / 12 days ago

• Vanilla+PostCSS as an Alternative to SCSS

  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 / 3 months ago

• When Vite ignores your Browserslist configuration

  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 / 5 months ago

• Simple reactions in HTML + CSS

  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 / 6 months ago

• why do some ppl put vendor prefixes(webkit...) on a specific place like div or p . i tend tu put them as a global rule ???

  Something like this https://postcss.org/. - Source: Reddit / 6 months ago

• Advice for experienced dev taking on front-end role?

  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: Reddit / 7 months ago

• Setup TailwindCSS, postcss and esbuild on Rails 7

  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 / 8 months ago

• To fly you need a tailwind

  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 / 11 months ago

• Ember.js: Installing Tailwind CSS

  The goal is to make your Ember.js app integrate with PostCSS and use Tailwind as a plugin. - Source: dev.to / 11 months ago

• CSS Framework VS CSS Preprocessor

  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: Reddit / 11 months ago

• PurgeCSS & styled-components: Does It Work?

  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 1 year ago

• tailwind: no simple way to get started

  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: Reddit / about 1 year ago

• tailwind: no simple way to get started

  PostCSS is a whole other package. Tailwind can integrate with PostCSS. - Source: Reddit / about 1 year ago

• Supercharge your CSS with Tailwind

  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 1 year ago

• Engineering Design Systems In 2022

  Making your library as modular as possible will aid with the adoption of it. A team should be able to pick and choose which parts they need of your system to keep their application as performant as possible. There are numerous tools you can use to aid with this process such as Sass, PostCSS and TailwindCSS. - Source: dev.to / about 1 year ago

• How to Install Shoelace with Rails 7, esbuild, and PostCSS

  Thankfully, what is far more appealing regarding Rails 7 is its additional support for esbuild and PostCSS, two very fast, very capable, and extremely customizable frontend build tools. While I'm bummed that there's no real config file shipping out of the box for esbuild, such things can be put together with the right resources. Maybe the community can step up. - Source: dev.to / over 1 year ago

• How to Migrate a Rails 6 App From sass-rails to cssbundling-rails

  Use Tailwind CSS, Bootstrap, Bulma, PostCSS, or Dart Sass to bundle and process your CSS, then deliver it via the asset pipeline in Rails. This gem provides installers to get you going with the bundler of your choice in a new Rails application, and a convention to use app/assets/builds to hold your bundled output as artifacts that are not checked into source control (the installer adds this directory to .gitignore... - Source: dev.to / over 1 year ago

• Getting started with Svelte, Tailwind, and Nrwl NX

  PostCSS is a CSS processor that Tailwind relies on to do its magic. - Source: dev.to / over 1 year ago

• Those of you who have built your own personal website or blog, what tech stacks do you use?

  For my last two personal websites I used Svelte (not Sapper or SvelteKit), married up with Page.js for client-side routing and Tailwind (+ PostCSS) for styling stuff. The sites are hosted from AWS S3 buckets with CloudFront for the CMS stuff. And because these projects are entirely personal I've not had to do a lot of worrying about the toolchain: both codebases are in git repositories; testing (when I bother) is... - Source: Reddit / over 1 year ago

• Set of Free (MIT) Transactional Email templates built using Tailwind CSS

  The included Maizzle configuration post-processes all of your HTML using various PostCSS plugins. In the end, you just write normal HTML with Tailwind and Maizzle takes care of building your HTML templates out, and spits them into the /dist directory when complete. - Source: dev.to / over 1 year ago

• Intro to ViteJS

  Under the hood, Vite uses esbuild. For CSS, it can handle PostCSS if you add a config for it, or css-modules if you add .module.css files, or sass. It will also make liberal use of the import.meta to add some sugar methods like glob imports or adding environment variables. You can switch the build to use terser and get a slightly smaller build, but it is a little slower. In my regular usage, I don't notice a huge... - Source: dev.to / over 1 year ago