-
-
Notifications
You must be signed in to change notification settings - Fork 211
Conversation
This fixes an issue where the generated CSS was taking into account the relativeFontPath but the HTML demo was not.
I am not sure why this test is failing on travis-ci. All tests pass locally and when I run the tests without the clean at the end this is the result of the tests. As you can see there are no files that are outside of the
|
It's only failing on node v5+. What version of node are you running locally? |
Yeah, and I don’t think it fails because of your changes. It fails in master with Node 5.7.0 (was fine in 5.6.0) on my Mac too. |
Here is the reason: gruntjs/grunt-contrib-clean#85 |
Ah, yes that would explain it. I am running Node v 5.3.0. |
Looks like it’s Node bug (see the comments by the link above). |
Use relativeFontPath in HTML demo
Out in 1.2.0, thanks! (As well as new Node 5.7.1 that fixes a bug that caused tests to fail.) |
My demo.html crashed because the variable o.relativeFontPath is an empty string and new RegExp with an empty string appends it to anything. My demo.html contains the following: That's the expected code: Temporary I fixed it with a short if condition. I'm not sure if this would be the best solution: fry2k@bab011e A Temporary solution for me is also set the option options.relativeFontPath to the same value like dest at the grunt task-definition dest, destCss and destHtml have all the same path at my env: "dist/font" |
This fixes an issue where the generated CSS was taking into account the relativeFontPath but the HTML demo was not.