-
Notifications
You must be signed in to change notification settings - Fork 56
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
An updated fork #15
Comments
@gzuidhof Is your package published to the npm registry? I tried running –
but this doesn't work! |
Hi paambati, I think you misspelled my name :) |
@gzuidhof Oops, so sorry! It works, thanks! Although, I wish to report an issue, but I notice the issue tracker isn't enabled for you repo. What would be a good place to do this? |
Ah.. I enabled it now. Not sure why it was disabled, perhaps it's a fork thing? |
For those interested, I just made a couple of additional improvements on yet another fork: |
As this package has not received a lot of attention / maintenance lately, I've forked a fork of this adding some fixes and improvements. You can replace your package to use
@gzuidhof/go-npm
insteadThe repo can be found here, here's the current list of changes:
I'm happy to merge the changes into here one day, but I'm not holding my breath :)
The text was updated successfully, but these errors were encountered: