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?