VSCode is indeed awesome for Vue. It supports pretty much any lang in any block properly, due to its support for embedded language contexts. If you have template lang="pug" and pug grammar plugin, it just picks it up. Also Vetur extension adds a lot of autocompletes and typescript support.

My problem is more with CSS and template support.

Here is Webstorm complaining about in a legit Vue v-for statement in a .vue single-page component.

And second image is what it does when I try to use PostCSS variables.

https://imgur.com/a/BNAa8

Aha! I see. Do you happen to have a repo I can clone to reproduce the problem? I'm interested in fixing that.

Vue's tooling is context aware. It knows when you're within a <style scoped> tag. I see that there's a PostCSS plugin: https://i.imgur.com/JTPlIEk.png

Theoretically, the tooling should be able to use that plugin's lexer rules. PostCSS already registers itself as a language (pcss) so Vue's tooling logic should be: "are we within a <style scoped> tag? search for PostCSS tooling; if if none found, use vanilla CSS."

It already does this for <style lang="scss">, so postcss should definitely work. The logic happens in https://github.com/JetBrains/intellij-plugins/tree/master/vu... if you want to explore it.

Yes I am using this PostCSS plugin: https://plugins.jetbrains.com/plugin/8578-postcss-support

But it's flawed. PostCSS is itself a host for plugins. So a WebStorm PostCSS plugin would need to allow user to select the PostCSS plugins that they are using.

Case in point: I use postcss-simple-vars but the WebStorm plugin assumes I use postcss-custom-properties. And so it fails me.

> Do you happen to have a repo I can clone to reproduce the problem? I'm interested in fixing that.

Yeah for a repro you just just need to do this: https://imgur.com/a/N2S2r

And you can see the warning when you hover over choices in the second image.

Very strange. This code is supposed to handle that: https://github.com/JetBrains/intellij-plugins/blob/f1b45bf1b...

I'll try repro'ing it.

Thanks, I appreciate your help.

It's gonna be a little while before I can scrape together the time to look at this. This week is gonna be a doozy. Sorry.

I think we should open a ticket in the appropriate place though. There's a good chance that a plugin maintainer can look into this and fix it quickly. It's such a clear example of brokenness, and should be pretty easy to fix.

I'm not quite sure where to raise the issue though. And I'm falling asleep, so that's all for now.

There are a bunch of bugs in their tracker for vue:

https://youtrack.jetbrains.com/issues/WEB?q=vue

So I figure it'll get fixed some day... probably after I move to another framework.