Skip to content
This repository has been archived by the owner on Oct 3, 2023. It is now read-only.

Add build rules for Bazel/Closure #53

Open
draffensperger opened this issue Apr 15, 2019 · 0 comments
Open

Add build rules for Bazel/Closure #53

draffensperger opened this issue Apr 15, 2019 · 0 comments
Assignees
@draffensperger
Labels
after-release Changes to make after initial NPM release

Comments

@draffensperger
Copy link
Contributor

Building with Bazel will enable local development that can change any part of the code in dependent packages and get quick incremental rebuilds.

Building with Closure will enable smaller JS bundles for use in <script> tags, and helps ensure that no Closure-incompatible changes would be introduced later on for users whose builds use Closure.

Relevant links:

The NPM/WebPack builds would continue to be supported after this change.
@draffensperger draffensperger added the after-release Changes to make after initial NPM release label Apr 15, 2019
@draffensperger draffensperger self-assigned this Apr 15, 2019
RenaultAI pushed a commit to RenaultAI/opencensus-web that referenced this issue Nov 20, 2019
@odeke-em
interceptor/opencensus: fix protocol misreadings
a6eec20 
* Return immediately if the first message doesn't
have a non-nil Node. Previously we leniently
spun 15 times as a best case retry but that's
unnecessary
* If the first message is valid and has spans, those
spans MUST be consumed and NOT discarded.

Fixes census-instrumentation#51
Fixes census-instrumentation#53
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@draffensperger draffensperger

Labels
after-release Changes to make after initial NPM release
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@draffensperger