Skip to content
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

Pixel values in custom property names are converting too #44

Closed
ryanve opened this issue Jan 25, 2018 · 0 comments
Closed

Pixel values in custom property names are converting too #44

ryanve opened this issue Jan 25, 2018 · 0 comments
Labels

Comments

@ryanve
Copy link

ryanve commented Jan 25, 2018

In our codebase we have some custom properties like --rem-16px: 1rem

If I run postcss-pxtorem with these then these variables are renamed like --rem-1rem: 1rem but I didn't expect that the property name would be replaced. Not sure if it's a big issue because I plan to remove those and replace with this plugin but still maybe there is a way to prevent that or is that the desired behavior?

2:14	⚠  variable '--rem-1rem' is undefined and used without a fallback [postcss-custom-properties]
45:14	⚠  variable '--rem-1rem' is undefined and used without a fallback [postcss-custom-properties]
48:14	⚠  variable '--rem-2rem' is undefined and used without a fallback [postcss-custom-properties]
@cuth cuth added the bug label Jan 25, 2018
@cuth cuth closed this as completed in e1467ab Mar 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants