-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Next... #1
Comments
would also be worth supporting specifying the name of the file where the URL contents is being saved (as opposed to just basing it on the base url). I've sent a pull request for this. |
BTW I see you merged my pull request (thank you!) -- what is the plan/schedule for the next release (which includes it)? |
There is nothing in the plan so far. Do you need any new features? |
It's only the change I sent in the pull request that I would like to be honest, the sooner the better really. |
just npm install the new one, please |
hmmmm that would work locally but won't work when I deploy this (via a server that doesn't have the fix). I can live with this for now but would be great to know when this makes it in the npm registry so I don't have to do a lot of hacks to pull the version with the fix. |
But, Release 0.0.6 has been publish to npm an hour ago.... |
oh right, that's what I was asking for -- I was not aware of that. |
yes |
The text was updated successfully, but these errors were encountered: