ai / autoprefixer-core

autoprefixer-core was depreacted, use autoprefixer

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

postcss-autoprefixer

jonathanong opened this issue · comments

any chance of another refactor that only exposes an autoprefixer plugin?

@jonathanong What benefits it can give to us?

Only postcss dependency? npm will not download postcss to autoprefixer-core if you plugin already use postcss (child package can take same dependency from parent).

i want to use it like another postcss plugin. that's all :) and maybe get rid of those postcss options. feel free to close this if you're aginst it.

autoprefixer-core is a just PostCSS plugin (just with .process(css, opts) shortcut)

What about a simple and stupid postcss-autoprefixer plugin

modules.exports = require("autoprefixer-core").postcss

with postcss as peerDep ?

Just to keep the same api as other postcss-* plugins ?

@MoOx yeap, common API will be nice.

But maybe we should fix PostCSS:

use(processor) {
    if ( typeof(processor) == 'object' && processor.postcss ) {
        processor = processor.postcss;
    }
    
}

I can release new PostCSS if everyone is agree.

Not sure it's a good idea. All tools don't use .postcss (example).

@MoOx @hail2u maybe we should unify .postcss?

I've already renamed PostCSS processor name. It'll release soon.

I'm not fan of this way to handle the issue, but why not...
I'll just be weird to have a similar snippet

postcss()
  .use(require("postcss-sha")())
  .use(require("postcss-blah")())
  .use(require("postcss-bla")())
  .use(require("autoprefixer-core")())

But it's not a big deal :)

@MoOx You can use

.use(require("autoprefixer-core"))

without brackets (just autoprefixer.postcss).

@hail2u Can we use just require('csswring').postcss?

@hail2u Can we use just require('csswring').postcss?

Yes.

@ai I know, I was just refering to the package name ;)
But nevermind it's not a big deal.

Released in 2.2.2. I also update all code examples with gulp-postcss.