-
-
Notifications
You must be signed in to change notification settings - Fork 425
Conversation
@tysongach Any chance you could look into this and possibly release a new bugfix version for v1? |
Pinging @whmii; he leads the Neat project. |
Ill take a look at this first thing mañana. I have to double check the sass spec but if all looks good ill merge |
@mfeltscher LGTM |
@whmii Thanks for merging! Are you going to release a new version which this fix is part of? |
@whmii Any chance for |
@whmii I'd also love to see a 1.9.1 with this fix, if you have a chance. |
Bumping in support of that last comment. |
@whmii Any news on this? |
Currently it is unlikely this will get patched. Unfortunately the way NPM works, if we patch an older version it becomes the 'newest' in NPM www site which means that many users inadvertently download it expecting v2.0… or v3.0… which can cause major problems w/ people who do not specify their npm packages properly (which is like … a lot…). 🙇 While this is super inconvenient, If it continues to be an issue I whiled recommend creating a fork of Neat w/ these changes or switching over to 3.0 which has a bunch of awesome new features. Sorry you are having these issues. |
Couldn't the release be created right before a new 3.x version? That should work around the issue. |
@whmii you can work around that by using the |
This fixes the following Sass warning: