-
Notifications
You must be signed in to change notification settings - Fork 172
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
Don't deploy .deb files to npm #121
Conversation
How are these |
During the bazel install step |
Thanks for raising. I'll try to do some investigation to see why bazel is outputting outside of the bazel directory. |
Using unpkg.com confirms that the bazel deb is no longer deployed to npm: https://unpkg.com/[email protected]/ |
@easyCZ actually, you were right to question this; the |
* upstream/master: Transport member of ServiceClientOptions should be optional (improbable-eng#125) Allow canceling unary calls (improbable-eng#124) CI should check that generated code has been committed (improbable-eng#127) Bumped to v0.7.8-pre (improbable-eng#123) Prepare 0.7.7 release (improbable-eng#112) Clean up Bazel Installation during Travis Build (improbable-eng#122) Don't deploy .deb files to npm (improbable-eng#121) Fix snake_cased oneof message are generated to incorrect types (improbable-eng#118) Make ServiceError optionally null (improbable-eng#116) Be explicit about the need for a CommonJS environment. (improbable-eng#108) Replace usage of `Object.assign` (improbable-eng#110) Add hint for Windows users (improbable-eng#107) Collapse Bazel Instructions in README (improbable-eng#106) Implement Client Streaming and BiDi Streaming for grpc-web (improbable-eng#82) Add support for jstype annotation (improbable-eng#104)
This reverts commit e9c9720.
Fixes #117