You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wanted to post the info here as well so people don't spin their wheels.
We reference grunt-svg-sprite as "^1.1.10" and end up with the latest after an 'npm install' on a fresh box.
Back in 1.1.10 grunt-svg-sprite referenced svg-sprite also as "^1.1.10"
The bug seems to be in svg-sprite, so even when I modify our reference to "1.1.10" to force a pull of the old version of grunt-svg-sprite, we still end up with the latest svg-sprite module (1.2.3 right now) which has the bug.
I think you've already fixed the svg-sprite reference to lock it down to an expected version in your packages.json with the "svg-sprite": "~1.2.3" declaration.
The text was updated successfully, but these errors were encountered:
I just posted the following issue (svg-sprite/svg-sprite#94) at https://github.com/jkphl/svg-sprite with details about a bug we're seeing with grunt-svg-sprite / svg-sprite.
I wanted to post the info here as well so people don't spin their wheels.
The text was updated successfully, but these errors were encountered: