-
Notifications
You must be signed in to change notification settings - Fork 60
Tag/release latest version to npm #336
Comments
Oh my bad! Yes, I can do that when I get back from work later today. I'll update this issue when I do it :) |
Hi @garetmckinley any chance you could do this when you get a minute? Think you may have forgot :D |
Just spent the last 2 days debugging an issue that I finally tracked down to this library. Looks like it would be resolved with #335, however my project is still broken because this update hasn't been pushed to NPM. This is a breaking change for me as it causes Netlify to error out because it's trying to log too many lines. Update: If anyone stumbles upon this in the future and the library still hasn't been updated, the fork from hehooleehoo contains the To resolve the issue I simply added that specific version of the lib via |
Yeah Please Update NPM. Just bump the version number and push. |
Hi ! |
@garetmckinley hey sorry to bother, but any chance you can do a release on this? Gonna be pulling directly from this directory until then (which isn't ideal hah). Thanks! |
Hi @garetmckinley,
A PR recently to remove some logs was approved and merged but as you haven't tagged a new version the default install from npm includes the console logs still. Could you tag /release the latest code please? 😄
P.S.Love this library, great work!
The text was updated successfully, but these errors were encountered: