Warning: parser with value "postcss" is deprecated. Use "css", "less" or "scss" instead.

[wbern]

./node_modules/.bin/prettier-stylelint src/assets/css/ahu.less --quiet
Warning: `parser` with value "postcss" is deprecated. Use "css", "less" or "scss" instead.

Not sure if it's because of prettier or this plugin.

https://prettier.io/docs/en/options.html#parser

[hugomrdias]

thank you for reporting i'll check this out, also need to update the vscode extension.

[kaelig]

I thought I'd open a PR here but the discussions over here started making my head spin!

[mmellado]

Is there any progress on this issue? There is a fork referenced above that seems to be solving it. On the other hand, the parser can simply become a new parameter (not sure if the new css parser would work with less and scss). It also seems like the vscode extension is using an older version of this package. I see discrepancies between running prettier-stylelint via command line and saving a file while using prettier.stylelintIntegration in vsCode (the ordes specified by stylelint-order is respected by the command line but not by the vscode extension)

[hugomrdias]

I'll address this issue and vscode extension in the weekend sorry for the delay Hugo Dias

…

On Nov 24, 2017 10:37, "Marcos Mellado" ***@***.***> wrote: Is there any progress on this issue? There is a fork referenced above that seems to be solving it. It also seems like the vscode extension is using an older version of this package. I see discrepancies between running prettier-stylelint via command line and saving a file while using prettier.stylelintIntegration in vsCode (the ordes specified by stylelint-order is respected by the command line but not by the vscode extension) — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#3 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AATLToM3Bu7FCP3PPMECswPQ3wG4HWvpks5s5pxXgaJpZM4QKt9M> .

[mmellado]

bump

[csantiago132]

hey man, great tool!! I am having this issue now so im wondering if im doing something wrong

[wbern]

@hugomrdias Looking at 0cfcb62 in @JonathanWolfe's fork, it seems this fix should be fairly easy, or is there more to it?

[kaelig]

In case this helps, @ismail-syed also forked the repo and applied a different fix than @JonathanWolfe: ismail-syed@1f0cf83

[icreatestuff]

I'm seeing a 'Couldn't resolve parser "postcss"' message in VSCode's Output panel whenever I save a .scss file. Sounds like the same/similar issue running v0.4.2

[wbern]

@kaelig @ismail-syed's fix is not a good one, because not everyone uses "css".

prettier supports automatically recognizing the type used, so it is completely fine to simply remove the property, like what @JonathanWolfe did.

[meszaros-lajos-gyorgy]

bump 2

[atipugin]

Any progress on it? Still getting this warning :(

[meszaros-lajos-gyorgy]

bump 3

[mazhermon]

bump 4 :)

[meszaros-lajos-gyorgy]

I'm afraid this project is no longer maintained :( Anyone care to fork it and continue the work?

[isellsoap]

In the meantime I published a temporary package, containing updated dependencies and the fix for this warning (which @ismail-syed opened this pull request for #6).

-> https://www.npmjs.com/package/prettier-stylelint-temp

[buyou0821]

$ prettier-stylelint --write -q 'src/**/*.{css,scss,less}' 
{ parser: "postcss" } is deprecated; we now treat it as { parser: "css" }.