-
Notifications
You must be signed in to change notification settings - Fork 662
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
module.exports.repository.replace is not a function #303
Labels
bug
M-T: A confirmed bug report. Issues are confirmed when the reproduction steps are documented
Comments
Same here. The module is broken now. |
Right. I did not expect that NPM would actually alter the package.json file. TIL. Getting a fix out now. |
UncannyBingo
added
the
bug
M-T: A confirmed bug report. Issues are confirmed when the reproduction steps are documented
label
Dec 20, 2016
palmerabollo
referenced
this issue
Dec 20, 2016
* First commit * Get the actual package name and version * passing tests and linter * Expose the version string as the user agent for WebAPI calls * Use GH repo name instead of node module name * Oh, linters * Add OS and node version to user agent * Add user agent to all outbound events * Fix a few bugs here and there. * Saner linting rules * We don't need that anymore, apparently. * Add user agent to outbound WS connections. Just in case. * Remove ability to override user agent * That was a not very good interface, let's remove it. * Allow users to make mistakes * One more test * Make it better again * JSDocs, yeah!
Merged
@rauno56 @palmerabollo Can you confirm the issue is resolved? |
It works now. Thank you @DEGoodmanWilson. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
M-T: A confirmed bug report. Issues are confirmed when the reproduction steps are documented
When I do:
The output I get is this:
It's because on the installed version the value of repository property in package.json is:
Which, I guess, is not expected.
On linux. Latest version.
The text was updated successfully, but these errors were encountered: