autoprefixer
postcss-preset-env
autoprefixer | postcss-preset-env | |
---|---|---|
31 | 9 | |
21,467 | 2,201 | |
0.2% | - | |
7.2 | 6.6 | |
17 days ago | about 2 years ago | |
JavaScript | CSS | |
MIT License | Creative Commons Zero v1.0 Universal |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
autoprefixer
- Vendor prefixes still relevant?
-
How do you handle browser compatibility?
Do you use Autoprefixer? https://github.com/postcss/autoprefixer
-
23 of the best Eleventy Themes (Starters) for 2023
Simple, fast, and a little bit opinionated, Eleventy Plus Vite features Eleventy 2.0.0-canary, the new Eleventy 2.0 Dev Server with live reload, Vite 3.0 as Middleware in Eleventy Dev Server (using eleventy-plugin-vite), build output post-processing by Vite (with Rollup), CSS/Sass post-processing with PostCSS including Autoprefixer and cssnano, a custom CSS/Sass structure, basic fluid typography based on Utopia, dark mode support, an RSS feed, XML sitemap, and — to top it off — perfect scores on Lighthouse.
- Need help understanding something. I have tried googling it and nothing is coming up.
-
The Complete Guide for Setting Up React App from Scratch (feat. TypeScript)
w/ postcss-preset-env(v7.8.3): convert modern CSS into something most browsers can understand, determining the polyfills you need based on your targeted browsers or runtime environments. It takes the support data that comes from MDN and Can I Use and determine from a browserlist whether those transformations are needed. It also packs Autoprefixer within and shares the list with it, so prefixes are only applied when you're going to need them given your browser support list.
-
How do I deal with CSS for Safari?
As others have said, you need to normalize. Also, you may need something like autoprefixer if you're using styles that have different vendor prefixes. https://github.com/postcss/autoprefixer
-
How to refactor an entire app to use something else instead of gap?
Mmm maybe it's not gap then, maybe it's some other property. Maybe autoprefixer could help. Or polyfills, as other user suggested.
-
Browserslist: building modern web apps for diverse global audience
Of course, we have great tooling for that: Autoprefixer, PostCSS and Stylelint for CSS transformation, Babel and Webpack for JavaScript transpilation and bundling, ESLint for code analysis, and many others.
-
10 GitHub Repositories to Become a CSS Master
Bulma uses autoprefixer to make (most) Flexbox…
- 34 Ways To Save Time On Manual Cross Browser Testing
postcss-preset-env
-
Vanilla+PostCSS as an Alternative to SCSS
Switching from a ready-made tool like Sass or a recommendation package like cssnext (deprecated since 2019) or PostCSS Preset Env (archived in 2022), to the modular PostCSS Preset Env plugin set we can choose a helpful and convenient set of future CSS features beyond the current stable client CSS.
-
What is PostCSS & Why should we care?
To enable the future CSS there is also a plugin called PostCSS Preset Env. This plugin will take the unreleased CSS selectors and change it to the present usable CSS. More info at PostCSS Preset Env
-
Getting started with Svelte, Tailwind, and Nrwl NX
Third, we enable the postcss-preset-env plugin, which adds support for many other cool things
- Why css in js over scss/css? Convince a team lead
-
PostCSS nesting with CSS variables isn't working in Tailwind CSS & Next.js
My PostCSS Config contains postcss-preset-env already which should support for CSS nesting. I also installed postcss-nested & postcss-css-variables, just in case.
-
Moving From Tailwind To Vanilla-er CSS
To solve this I used postcss-preset-env, which allowed me to define a "custom-media" with the name --viewport-lg and the value (min-width: 1024px). As postcss-preset-env also supported nested CSS this allowed for some pretty readable CSS.
-
CSS tips and tricks you won’t see in most of the tutorials
If you use PostCSS, postcss-preset-env[1] is pretty neat for reading up on the latest features. E.g. here is the place properties feature[2].
1: https://preset-env.cssdb.org/
-
Here's my website setup...
postcss-preset-env - it lets you use some cutting-edge CSS but understandable by modern browsers.
-
VSCode extensions for detecting CSS/SCSS invalid value errors?
https://stylelint.io https://github.com/csstools/postcss-preset-env
What are some alternatives?
rollup-plugin-postcss - Seamless integration between Rollup and PostCSS.
postcss-nested - PostCSS plugin to unwrap nested rules like how Sass does it.
browserslist - 🦔 Share target browsers between different front-end tools, like Autoprefixer, Stylelint and babel-preset-env
svelte-preprocess - A ✨ magical ✨ Svelte preprocessor with sensible defaults and support for: PostCSS, SCSS, Less, Stylus, Coffeescript, TypeScript, Pug and much more.
twin.macro - 🦹♂️ Twin blends the magic of Tailwind with the flexibility of css-in-js (emotion, styled-components, solid-styled-components, stitches and goober) at build time.
Sass - Sass makes CSS fun!
Visual Studio Code - Visual Studio Code
Tailwind CSS - A utility-first CSS framework for rapid UI development.
postcss-mixins - PostCSS plugin for mixins
plugins - 🍣 The one-stop shop for official Rollup plugins
nx - Smart Monorepos · Fast CI