Add support for CSS next

[szimek]

According to this comment one should create separate issues for individual features, so here it is :)

It would be great if cssnext nesting was supported. Currently, such syntax causes VS Code to report it as an error, e.g.

Are cssnext features in scope of this CSS language service or should they be implemented as an extension instead?

[aeschli]

CSSnext support is not planned. But we want to support whatever gets added to CSS specs.

[chriseppstein]

@aeschli I think this is good, it would be confusing for developers to not get syntax errors for invalid syntax intended for browsers unless they've opted into support for future features. That said, these features are usually on track to become css and so it's not entirely wasted effort to build support for the new features a bit early -- hidden behind feature flags to which devs would have to opt in.

Another approach would be for the css-next community to maintain a fork of this project, ideally with a git branch per future spec feature and a merge branch for release and when these specs reach maturity a PR could be submitted.

[praveenpuglia]

Couldn't this be made into an extension of some sort?

[sorenhoyer]

I would love cssnext support as well - if not built-in, then in an extension of some sort. cssnext really is the most logical pick today, over LESS and SASS imo.

[onetrev]

Hey @praveenpuglia @sorenhoyer and @szimek ... There is support for CSSNext with this PostCSS extension.

Unfortunately, as per the usual with VS Code not supporting cross file references ('imports'), you still can't get custom properties / variable autocomplete or Go To Declaration and such. But it's a start. It would be great to see more PostCSS support added to this extension or others created, as I agree it's very much the logical pick today and it's really gaining steam -- fast!

[szimek]

@onetrev Like you've noticed yourself in this comment, this vscode-postcss-language extension doesn't really support cssnext :/

[EECOLOR]

Would be nice if we could add these kinds of things using custom data.

[aeschli]

Closing as out-of-scope