Roman Dvornov

@pkuczynski Thank you for update! I checked properties that are already merged, will checked others when they are merged too.

Yep, I planned to add `.d.ts` to the project. @smelukov [worked on TypeScript definition](https://github.com/smelukov/csstree/tree/dts-file/types), but didn't finish. It will be great if someone finishes work.

CSSTree ignores comments expect for exclamation comments (i.e. `/*! .. */`) on top level. We may add top level `/*# .. */` comments as well. However, I'm going to remove...

I'm not sure such integration makes sense. However, technically that's possible. I did AST transformation csstree -> postcss and back in wrapper for CSSO: https://github.com/lahmatiy/postcss-csso

This issue is about https://csstree.github.io/docs/validator.html It has its own logic for a validation, in particular it exams at-rule's descriptors as a regular declarations what is wrong and the root cause...

Since [CSS Nesting](https://www.w3.org/TR/css-nesting-1/) is now on standardization path, a support for `&` selector (nesting selector) will be added in next releases as well as `@media` at-rule and rules with a...

`fallbackNode` and `onParseError` are parts of the parser, not tokenizer. A tokenizer produces tokens, a parser constructs a AST from tokens. A CSS tokenizer may not be suitable for SASS/Less/etc...

@TurtIeSocks Yes, `lexer` is a public API, but poorly documented. I guess, that's the reason why it's not typed well. You can see sources of [csstree-validator](https://github.com/csstree/validator/blob/master/lib/validate.js) and [stylelint-validator](https://github.com/csstree/stylelint-validator/blob/master/lib/index.js) as a...

@TurtIeSocks Yeap, that's ok

Nope, yet. I'd experimented with it but didn't finish. Now I reworking tokenizer, probably back to this issue after that. It would nice to know what is your use case?