We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New PostCSS 5.0 brings custom syntax, so you can convert JS object to PostCSS AST without stringifing/reparsering step.
The text was updated successfully, but these errors were encountered:
Amazing :) I'll check it out these days. One question though, does it work synchronously?
Sorry, something went wrong.
Sync. We can add async parsers in next release, but why you need it?
Perfect, I need it to be sync because of the way babel works. I'll give it a go then :) Thanks a lot for bringing it up again
On Thu, Aug 20, 2015 at 12:39 PM Andrey Sitnik [email protected] wrote:
Sync. We can add async parsers in next release, but why you need it? — Reply to this email directly or view it on GitHub #3 (comment).
— Reply to this email directly or view it on GitHub #3 (comment).
No branches or pull requests
New PostCSS 5.0 brings custom syntax, so you can convert JS object to PostCSS AST without stringifing/reparsering step.
The text was updated successfully, but these errors were encountered: