-
Notifications
You must be signed in to change notification settings - Fork 9
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
point apigeetool to npm registry module #15
Comments
We used fork'd repo of apigeetool because the turn around time to fix a bug of apigeetool in the main repo and publish the new npm is huge . But we can fix it in the fork and already start using it(and raise a PR). What certificates issues are you seeing ? Is there another way to solve it other than changing the apigeetool reference to public npm ? |
Find part of the npm debug log having problem with the self signed certificate.
|
I don't see this problem in my system. |
Its better to have a fix rather then a workaround, If the apigeetool is now upto date and published to npm we should point apigeetool from the npm registry. |
edge-launchpad/package.json
Line 4 in 60772be
need to change this and point it to the apigeetool repo from the npm registry
using local reference is causing certificates issues
The text was updated successfully, but these errors were encountered: