by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Sep 23 22:57
    illepic commented #1419
  • Sep 23 22:47

    ai on master

    Fix visiting parent on nested c… (compare)

  • Sep 23 21:54

    ai on master

    Add Processors docs (compare)

  • Sep 23 21:45

    ai on master

    Call RootExit on node changes a… (compare)

  • Sep 23 17:03

    ai on 8.0.9

    (compare)

  • Sep 23 17:03

    ai on master

    Release 8.0.9 version (compare)

  • Sep 23 17:00

    ai on master

    FIx a way to rebuild PostCSS 7 … (compare)

  • Sep 23 16:10
    illepic commented #1419
  • Sep 23 15:51

    ai on master

    Add missing Transformer type to… (compare)

  • Sep 23 15:51
    ai closed #1423
  • Sep 23 14:58
    illepic commented #1419
  • Sep 23 13:32
    enrique-ramirez commented #1419
  • Sep 23 10:11
    Ankcorn commented #1419
  • Sep 23 09:47
    pmdartus opened #1423
  • Sep 23 05:51
    illepic commented #1419
  • Sep 23 02:16

    ai on master

    Add author to changelog (compare)

  • Sep 23 02:12
    ai commented #1419
  • Sep 23 02:10

    ai on 8.0.8

    (compare)

  • Sep 23 02:10

    ai on master

    Release 8.0.8 version (compare)

  • Sep 23 02:04
    ai closed #1419
Marcello
@marcebdev
The default browser list is supposed to support all browsers from what I can see so not sure
Andrey Sitnik
@ai
show your code
do you use it with flexbox or with grid?
Marcello
@marcebdev
I'm using it with flexbox, I know it only has default support on newer Firefox versions from caniuse but the whole point of postcss-env-preset is supposed to be able to do this, no?
.frame {
  display: flex;
  column-gap: 30px;
}
as I mentioned it wasn't working on Chrome before either, hence why I added preset-env but even with the plugin Safari is not playing nice
Andrey Sitnik
@ai
I afraid that it is a limit of gap polyfill
it works well to polyfill gap for grid
@jonathantneal am I right? should we show a warning on gap and display: flex if we have a browser without gap support for flexbox?
Marcello
@marcebdev
Ah ok, appreciate the insight... I guess for now I will work on making margins work. At least I know I'm not going crazy trying to figure out what is wrong
@ai A warning would be awesome imo luckily I double-checked on safari or I wouldn't have known
Gabo
@GaboPlums_twitter
Hello... I'm a new developer
Andrey Sitnik
@ai
hi :)
Gabo
@GaboPlums_twitter
I wanna learn more about css
At this moment I'm working with tailwind framework
Is very easy and usefull
Andrey Sitnik
@ai
I agree
Gabo
@GaboPlums_twitter
@ai How long have you been working with tailwind?
Andrey Sitnik
@ai
I do not use Tailwind CSS
But I heard the same feelings from the collegues which I trust
Gabo
@GaboPlums_twitter
It sounds great ... you are frontend or full stack?
Andrey Sitnik
@ai
I was a fullstack (Ruby), but not a frontend
But I can do Node.js :) Just do not have a project to be a fullstack
Gabo
@GaboPlums_twitter
Are Ruby and Node.js similar?
Andrey Sitnik
@ai
nope :) very different
Jonathan Neal
@jonathantneal
@marcebdev, the issue with flexbox gap is, as Andrey pointed out, that there is no straightforward way to do it.
One plugin in pursuit of this is https://github.com/limitlessloop/flex-gap-polyfill
The issues are those opened by the author, who is using Custom Properties and margin to simulate the gap. This introduces a number of limitations on the implementation.
With limited support in browsers at the time of this writing, the polyfill would need to be very robust. https://caniuse.com/#feat=flexbox-gap
Jonathan Neal
@jonathantneal
I would recommend you sooner use CSS Grid and the Autoprefixer polyfill. At least then you’re targeting your polyfill squarely at IE11, which reduces your test cases to a single browser.
Joseph Kaptur
@josephkaptur
Hello! I think I've found an edge-case bug in PostCSS. I'm excited to fix it, but I figured I would start here to make sure it really is a bug.
If you have an AST where a node root has child nodes [a, b, c], and you have other nodes d and e, then calling a.replaceWith(a, d, e) results in root having the children [d, e, b, c], not [a, d, e, b, c], as I would expect
Andrey Sitnik
@ai
@josephkaptur Yeap, it is a bug. Send PR to ose branch.
Joseph Kaptur
@josephkaptur
Thanks very much. Should I create an issue on GitHub as well, or just send the PR?
Andrey Sitnik
@ai
@josephkaptur just PR
Jonathan Neal
@jonathantneal
That’s a really cool bug. I enjoyed your description and found it easy to follow, @josephkaptur.
2 replies
@ai, is the ose branch becoming the main? I don’t want to get excited too soon.
4 replies
Ryan Zimmerman
@RyanZim
What, gitter has threads now?
3 replies
Marcello
@marcebdev
Just wanted to double check, there seems to be no polyfill for the :not css selector when using postcss-preset-env, does that sound right?
3 replies
Elliot Fouts
@elliotfouts_gitlab
hey guys i just found postcss-env-function on github and i'm having some issues configuring it with my react app. In the section of documentation for react-app it says to use the method postcssEnvFunction and pass in some options. However, under the options tab in the main readme they use the method postcssCustomProperties to import the files. Which of these methods do i need to use to get env() working?
10 replies
Jonathan Neal
@jonathantneal
I need to setup notifications for Gitter. I am just lucky to check in every few days.
Jonathan Neal
@jonathantneal
I’m pretty desperate to work on PostCSS stuff.
Jonathan Neal
@jonathantneal
Our production CSS was completely broken using the client-side custom properties polyfill. We had to withhold deploying the plugin, but that meant I was "officially" authorized to spend the day working on a new client-side Custom Properties polyfill for IE11. I got close to finishing. Today, I have some other tasks to wrap up, but I may have a new plugin for this coming soon.
Jonathan Neal
@jonathantneal
:point_up: Happy news! I was able to fix half the problem, and the author has already released the fix. Once I fix the other half, I will move this plugin into PostCSS Preset Env.
I’m sorry that I’m super behind on this, but what kind of support is needed for CSSNano releases? I wonder if I can cut some time that could be useful there.
Evilebot Tnawi
@evilebottnawi
I am afraid that cssnano is dead, I don't have time on this project, and no contributors, it is so bad, bad I can't nothing here :disappointed:
Ben Briggs
@ben-eb

I'm kind of stuck there too. Actually I haven't worked for a long time with CSS so it's hard for me to justify contribution as relevant in some way to what I'm doing. Furthermore it means I can't review code that is going in because I'm not working day-to-day on CSS, so I have no idea about edge cases.

I also worry about PostCSS 8 migration. It will be very painful (and necessary) to do refactoring work around this. I am afraid I don't have any good answers on how we manage that. All I can say is I'm sincerely grateful to those who have contributed to the project.

Jonathan Neal
@jonathantneal
Do I have permissions in that project. I don’t want to buck our tradition of PRs before permissions, but I know the folks at Vercel are building their own copies of CSSNano, and with permissions I could help them get those fixed cuts into proper releases.
Or may I have permissions to do that, @ben-eb, @evilebottnawi ?
Benjamin Nash
@benash
Hi, does anyone know of a plugin that achieves what's done by composes in CSS modules and @apply in Tailwind? Such functionality would be helpful in using atomic/functional CSS classes.
Ben Briggs
@ben-eb
@jonathantneal No objection from me. :)