home.social

#postcss — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #postcss, aggregated by home.social.

fetched live
  1. 𝗕𝘆, 𝗯𝘆 𝗖𝗦𝗦𝗡𝗲𝘅𝘁, 𝗵𝗲𝗹𝗹𝗼 𝗽𝗼𝘀𝘁𝗰𝘀𝘀-𝗽𝗿𝗲𝘀𝗲𝘁-𝗲𝗻𝘃:

    #Node #CSS #PostCSS

    thewhale.cc/posts/by-by-cssnex

    As CSSNext is now deprecated you can use instead the Postcss plugin "PostCSS Preset Env" to lets you use modern CSS in your style sheet.

  2. Watch out: Fake npm packages are impersonating a popular PostCSS tool to drop a #Windows RAT and steal passwords stored in Chrome.

    Listen or Read: hackread.com/fake-npm-packages

    #npm #PostCSS #Cybersecurity #Malware

  3. Watch out: Fake npm packages are impersonating a popular PostCSS tool to drop a #Windows RAT and steal passwords stored in Chrome.

    Listen or Read: hackread.com/fake-npm-packages

    #npm #PostCSS #Cybersecurity #Malware

  4. 𝗕𝘆, 𝗯𝘆 𝗖𝗦𝗦𝗡𝗲𝘅𝘁, 𝗵𝗲𝗹𝗹𝗼 𝗽𝗼𝘀𝘁𝗰𝘀𝘀-𝗽𝗿𝗲𝘀𝗲𝘁-𝗲𝗻𝘃:

    #Node #CSS #PostCSS

    thewhale.cc/posts/by-by-cssnex

    As CSSNext is now deprecated you can use instead the Postcss plugin "PostCSS Preset Env" to lets you use modern CSS in your style sheet.

  5. 𝗕𝘆, 𝗯𝘆 𝗖𝗦𝗦𝗡𝗲𝘅𝘁, 𝗵𝗲𝗹𝗹𝗼 𝗽𝗼𝘀𝘁𝗰𝘀𝘀-𝗽𝗿𝗲𝘀𝗲𝘁-𝗲𝗻𝘃:

    #Node #CSS #PostCSS

    thewhale.cc/posts/by-by-cssnex

    As CSSNext is now deprecated you can use instead the Postcss plugin "PostCSS Preset Env" to lets you use modern CSS in your style sheet.

  6. Фиксим залипающий hover на мобильных устройствах

    Что мы проверили: Залипающий hover на мобильных устройствах – частый баг. Раньше мы решали это просто плагином PostCSS Hover Media Feature, он оборачивает все псевдоклассы :hover в медиазапрос @media (hover: hover) {}. Так мы проверяли поддержку hover и отключали его на мобилках. Но во время тестирования одного проекта оказалось, что на некоторых устройствах hover продолжает залипать.

    habr.com/ru/articles/955650/

    #CSS #scss #postcss #plugin

  7. CSS-медиазапросы без min- и max-. Как работает новый синтаксис и стоит ли переходить?

    Разбираем новые возможности CSS Media Queries Level 4 — логические операторы сравнения, которые делают код более читаемым и интуитивным. От (min-width: 768px) and (max-width: 1024px) к простому (768px <= width <= 1024px) . Зачем это нужно и как с этим работать?

    habr.com/ru/articles/929530/

    #медиазапросы #media_queries #вёрстка #адаптивная_вёрстка #css #css3 #postcss #диапазоны_css

  8. postcss-color-golf plugin 1.2.0 released!
    github.com/xero/postcss-color-

    rgb(255,0,0) → red
    aliceblue → #f0f8ff
    #aabbcc#abc;
    rgba(255, 170, 187) → #fab
    rgba(255, 170, 187, 0.8) → #fabcc
    rgb(255, 255, 255, 1) → #fff
    rgb(0, 255, 0, 0.8) → #0f0c
    fuchsia → #f0f

    #postcss #css #csstransforms #color #codegolf #golf #plugin

  9. postcss-color-golf plugin 1.2.0 released!
    github.com/xero/postcss-color-

    rgb(255,0,0) → red
    aliceblue → #f0f8ff
    #aabbcc#abc;
    rgba(255, 170, 187) → #fab
    rgba(255, 170, 187, 0.8) → #fabcc
    rgb(255, 255, 255, 1) → #fff
    rgb(0, 255, 0, 0.8) → #0f0c
    fuchsia → #f0f

    #postcss #css #csstransforms #color #codegolf #golf #plugin

  10. #PostCSS もそろそろ使わなくてもいいかもな…

  11. #PostCSS もそろそろ使わなくてもいいかもな…

  12. We lost so much when dropping Sass for PostCSS.

    CSS built-in nesting is awkward, static variables can be useful actually, and what's the point of dropping a consistent API with good DX if we're still transforming our stylesheets anyways?

    Chaining together interoperable PostCSS modules to accomplish half of what Sass can do is nearly impossible.

    #CSS #Sass #PostCSS #WebDev

  13. We lost so much when dropping Sass for PostCSS.

    CSS built-in nesting is awkward, static variables can be useful actually, and what's the point of dropping a consistent API with good DX if we're still transforming our stylesheets anyways?

    Chaining together interoperable PostCSS modules to accomplish half of what Sass can do is nearly impossible.

    #CSS #Sass #PostCSS #WebDev

  14. After reading this, checked my existing styling as processed through autoprefixer, found the few vendor prefixes that had been added, and manually added them to my styling — so it now doesn’t require any additional tools for cross-browser compatibility.

    weser.io/blog/vendor-prefixes-

  15. Post >> TIL some info about PostCSS Preset Env and Browserslist • When all else fails, I go to the source and ask.

    brycewray.com/posts/2024/02/ti

  16. Just learned something I’d hoped was true: if your project has a more updated version of browserslist than what’s in postcss-preset-env, postcss-preset-env will use the better data instead of what’s in its own browserslist dependency:

    github.com/csstools/postcss-pl

  17. Post >> Using Lightning CSS with Hugo: back to the workaround • Why a clear separation between dev mode and prod mode made sense.

    brycewray.com/posts/2024/02/us

  18. I made a contribution to browserslist:

    github.com/browserslist/browse

    I have been trying to get the Lume static site generator to run inside a #Dropserver sandbox, but I have been running into all kinds of issues: some modules written for #NodeJS assume they have read permissions for the entire disk, and error out when you run them with restrictive permissions. Any project that uses #PostCSS + #autoprefixer (ie most build systems) will hit this.

    github.com/browserslist/browse

    1/2

  19. I made a contribution to browserslist:

    github.com/browserslist/browse

    I have been trying to get the Lume static site generator to run inside a #Dropserver sandbox, but I have been running into all kinds of issues: some modules written for #NodeJS assume they have read permissions for the entire disk, and error out when you run them with restrictive permissions. Any project that uses #PostCSS + #autoprefixer (ie most build systems) will hit this.

    github.com/browserslist/browse

    1/2

  20. (Restoring an earlier item that I briefly removed when I encountered, and subsequently fixed, a local glitch...)

    Post >> Using Lightning CSS with Hugo — without workarounds • With a little tinkering, there’s no need for that PostCSS plugin I recently mentioned.

    brycewray.com/posts/2024/02/us

  21. Any #PostCSS users know how I can include other CSS files with a prefix. Use case is that I want to import two files - light and dark themes for #highlightjs, but dark mode needs all selectors to be scoped with an additional `.dark` class prefix

  22. New post >> Using Lightning CSS with Hugo • Does Hugo natively support Lightning CSS? No, but there’s a neat workaround for that.

    brycewray.com/posts/2024/01/us

  23. ...well I did promise a part 3, so let's close it off!

    JAVASCRIPT WEB TOOLS.... but a Trading Card Game! (PART 3 of 3)

    21: #PostCSS - "A tool for transforming CSS with JavaScript plugins."

  24. ...well I did promise a part 3, so let's close it off!

    JAVASCRIPT WEB TOOLS.... but a Trading Card Game! (PART 3 of 3)

    21: #PostCSS - "A tool for transforming CSS with JavaScript plugins."

  25. Mit `@apply` macht #Svelte und #Tailwind durchaus Spaß. Caveat: #PostCSS muss an sein.

  26. Как автоматизировать использование дизайн токенов с помощью Stylelint и PostCSS

    Привет, Хабр! Меня зовут Саша и вот уже 7 лет я работаю фулстек разработчиком и пишу на C# и TypeScript/React. Сегодня я хотел бы поделиться своим небольшим успехом в автоматизации. В какой-то момент я понял, что во время код ревью я указываю разработчикам на одни и те же ошибки. Но, что ещё хуже, я сам время от времени допускаю эти ошибки. Сегодня хочу рассказать об одной из таких проблем, которую я решил с помощью PostCSS + Stylelint, и о том, как я это сделал. Статья будет полезна для разработчиков, которые уже используют или собираются использовать дизайн токены. Начнём!

    habr.com/ru/articles/779492/

    #javascript #stylelint #postcss #дизайнтокены #автоматизация #cssпеременные #линтеры #typescript #плагины

  27. Looking to move away from Sass (#SCSS) to pure #CSS now that pretty much all functionality exists in #CSS. The only remaining feature that I would need some kind of processor/bundler for is for combining different files (I like to separate everything).

    Any tips for a good bundler? Is #PostCSS the thing to go for?

    #WebDev #WebDevelopment

  28. Looking to move away from Sass (#SCSS) to pure #CSS now that pretty much all functionality exists in #CSS. The only remaining feature that I would need some kind of processor/bundler for is for combining different files (I like to separate everything).

    Any tips for a good bundler? Is #PostCSS the thing to go for?

    #WebDev #WebDevelopment

  29. #Development #Reviews
    CSS is fun again · Why it’s time to revisit CSS if you have lost sight of it ilo.im/15ek6d

    “The pace of new features has accelerated so much, that I envy those who are just learning CSS today.” — Jeff Sandberg

    _____
    #WebDev #Frontend #CSS #Sass #PostCSS

  30. @nachtfunke ah. okay. thanks for that clarification. that makes sense actually. but is that specific to sass?
    Are you the guy* who was talking about #PostCSS ?

    ( *RE: sleep disorder. sometimes zombie functioning. i remember tags and avatars. but it's kind of like trying to remember a near blackout. function also of very poor sleep habits, no real schedule. a person like me needs strict discipline to avoid those symptons )

  31. Starting to think about transitioning off of Sass to “modern CSS” with postcss-preset-env for downlevel transformation. Mostly because someday we’ll have native CSS nesting support which should really reduce the size of stylesheets. I haven’t found a great PostCSS replacement for inlined constants like Sass has though. #CSS #postcss #sass

  32. #Development #Releases
    Native CSS nesting support arrives in the big three browsers · The release of Firefox 117.0 completes the trifecta ilo.im/150a5r

    _____
    #WebDev #Frontend #Browser #CSS #CssNesting #Chrome #Firefox #Safari #Sass #PostCSS

  33. #tailwind "It's an obtuse abstraction"
    pdx.su/blog/2023-07-26-tailwin

    I'd add, Tailwind is also primarily a business model around CSS.
    Utility classes weren't new, the tooling was already there (#PostCSS) so they "just" built a nice looking design system with a proprietary #CSS #framework.

  34. Kinda hilarious that not only have to wait for modern browsers to fully implement a (finalised) CSS spec, but also wait for the text editor (or its extensions) to support it too
    VSCode: github.com/microsoft/vscode/is
    PostCSS Language Support: github.com/csstools/postcss-la

    #WebDev #VScode #PostCSS

  35. @kevtiq CSS has come so far!

    I’m in same position right now, but using #WithAstro. The only thing I still use from #scss is nesting and loops. I like using mixins, but i think i can do without them.

    I know there are a couple #PostCSS plugins for nesting. But I love the brevity of looping over a map and their reusability. Is #nestedcss standardized yet?

  36. Phew, I know why I hate setting up and maintaining build tool chains. TailwindCSS nested in PostCSS nested in Webpack and stuff like taht is not exactly what I would call fun, when coding.

    #WebDev #Webpack #TailwindCSS #PostCSS

  37. #oklch() in the #CSS Color 4 specification looks really promising for easier #color management. It's not quite ready for prime time, but you can already use it with #PostCSS.

    Here's a thorough explanation.
    evilmartians.com/chronicles/ok

  38. Big thanks to @BryceWray for providing the solution to my long term problem of cache-busting using @eleventy and Tailwind CSS using PostCSS. Been racking my tiny brain for ages trying to figure out a solution. His post can be found at
    brycewray.com/posts/2020/11/us

    #eleventy #postcss #development

  39. I'm like forever waiting for PostCSS (and their plugins) to support CSS Color 5. I just want to manipulate the lightness of HSL and alpha of RGBA, that's all.

    #CSS #PostCSS #webdev #frontend

  40. @cuboci @wiverson Sure... but technically the "easy" answers you're giving the #sveltekit wizard are getting handed off to #vite, #postcss, etc. via config magic. Again, you probably want something where the integrations are more intentional.

    I guess if you really want to see how the sausage gets made, you should play with #vanilajs and #webpack, #vite, etc before even playing with a framework?

    No matter what, I feel ya. There's no getting around the magic :P