Skip to content

Parsing errors from tailwind default config #114

New issue

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

Closed
m11m opened this issue Sep 15, 2019 · 1 comment · Fixed by #120
Closed

Parsing errors from tailwind default config #114

m11m opened this issue Sep 15, 2019 · 1 comment · Fixed by #120

Comments

@m11m
Copy link

m11m commented Sep 15, 2019

I had a parsing error on the following css:

flex: 1 1 0%;

I'm pretty sure this is legal css, the unit (% in this case) is optional?

Error printed out as:

Error: Failed to parse declaration "flex: 1 1 0%"

Here is the line in tailwind default config, I can work around this, but maybe it makes sense to support optional units on 0 ¯_(ツ)_/¯ :

https://github.com/tailwindcss/tailwindcss/blob/beff1383533973baeb33436d7c31651b9ea751a8/stubs/defaultConfig.stub.js#L209

@jacobp100
Copy link
Contributor

jacobp100 commented Sep 16, 2019

This one is a bug! I'll try and get it fixed within the next few days

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants