-
-
Notifications
You must be signed in to change notification settings - Fork 188
NaNpx values when using REM units #210
Comments
It's probably a pixrem bug /cc @iamvdo |
Smaller test case: html {
font-size: 0.625vw;
}
h1 {
font-size: 6rem;
} Output: html {
font-size: 0.625vw;
}
h1 {
font-size: NaNpx;
font-size: 6rem;
} |
Thanks @ben-eb! I'll report that in |
Waiting for this robwierzbowski/node-pixrem#45 |
Closed by robwierzbowski/node-pixrem@9ccf84f |
Hmm just did to no avail. |
Can you double check you have node-pixrem 2.0.1 please ? |
I can't have that since cssnext specifies pixrem 1.* https://github.com/cssnext/cssnext/blob/master/package.json#L41 |
Unfortunately the unit test fails with microtime@1.5.0, which is a dev dependency of Hmm seems there is some info about telling travis to use GCC 4.8 and here. I don't have time to do more but wanted to share the info. Of course the Windows issue seems to be totally unrelated: https://ci.appveyor.com/project/MoOx/cssnext/build/279 |
See #219 for fixing unrelated issues to this PR. |
This will have to wait #202 :/ |
node_modules/.bin/cssnext -V
:1.8.4
I haven't been able to create a reduced test case to show this, so I'm dumping my entire
css
file here. Sorry for the lengthy post.Running cssnext with the following command:
node_modules/.bin/cssnext example/**/*.src.css example/css/all.min.css
Note that
node_modules/.bin/cssnext --no-rem example/**/*.src.css example/css/all.min.css
obviously doesn't produce anyNaN
values.On:
Produces:
Happy debugging! 👍
The text was updated successfully, but these errors were encountered: