* Add v0.25.1 to changelog (#213)
* Attempt to fix `make publish` (#214)
Historically, `make publish` has left lingering changes to `/dist` that
are (currently...) necessary for browser usage but don't make it into
the correct build.
Moving the `make build` step into the npm-controlled `version` step and
then adding the `/dist` changes should (hopefully!) fix this.
See https://docs.npmjs.com/cli/version.html for more information.
* 0.25.1
* fix: 'method' was always GET. simplify _shouldTrace. (#217)
* fix: 'method' was always GET. simplify _shouldTrace.
* include username/password in fetch impl
* remove user:pass from trace + note
* Fix timestamp conversion for protobuf transport (#221)
Previously, we converted microseconds -> milliseconds -> seconds +
nanoseconds. By converting first to milliseconds, we lost some
granularity at the sub-millisecond level.
* Fix missing clock offsets over proto transport (#222)
It seems that we must stringify our ints before setting them in order
for them to actually get sent 😬 Without this, offsets won't get applied
to spans sent via proto.
To see this in action:
1. Emit spans over protobuf using an earlier version of the JS tracer
2. Open the trace in LightStep
3. Using the network tools, inspect the response body containing the
trace
4. Observe that the JS spans all have `timestamp_offset` == 0
5. Repeat steps 1-3 using the fixed tracer
6. Observe that after the fix, `timestamp_offset` is no longer always 0
* Update CHANGELOG for v0.25.2
* 0.25.2
* Add additional item to CHANGELOG for v0.25.2
* Upgrade eslint (#218)
* upgrade eslint+friends, and autofix code
* fix remaining eslint errors or ignore
* update babel config to handle spread
* feat(TracerImpl): Optionally empty span buffer on max error streak (#226)
* feat(TracerImpl): Optionally empty span buffer on max error streak
refs #225
* fix(TracerImpl): Updates docs for _clearSpanRecordsIfMaxErrors
* fix(TracerImpl): option `clear_span_buffer_consecutive_errors` naming
* README: added documentation
* Update README.md
* Update README.md
* Updating Changelog for 0.26.0
* fix(fetch): PUT/POSTs were failing (#227)
Anything with a body was failing when excluded from tracing due to using
the initial input object instead of the created Request. Creating a new
request from an old request consumes the old request unless explicitly
cloned.
* Require node >= v8 (#228)
* Require node >= v8 and test all supported versions in CI
* Test version matrix in CI
* Fix 'engines' field
* updating package-lock.json pre-release
* 0.26.0
* 0.27.0
* Updating changelog
* fix: Baggage items propagation from parent to child (#233)
This PR implements context propagation from parent to child in a similar way as the [GoLang library](https://github.com/lightstep/lightstep-tracer-go/blob/master/span.go#L58-L63)
when a new span is created the baggage items get copied from the parent context to the child context.
Also it implements the methods _setBaggageItem and _getBaggageItem on the span, which are meant to be overriden
by implementors according to [opentracing specification for JS](https://github.com/opentracing/opentracing-javascript/blob/master/src/span.ts#L197-L204).
* export SpanContext (#230)
Fixes #229
* 0.28.0
* Updating Changelog for 0.28.0
* Update CHANGELOG.md
* Support React Native (#235)
* Adding checks for window and document undefined
* Removing Dist from repo
* Making browser detection more modular
* Adding dist back in since we don't build after install
* Updating to be more modular
* Update options_parser.js
* Regenerating dist
* Trim leading 0s when injecting in b3 propagator (#238)
* trim leading 0s when injecting in b3 propagator
* fix whitespace
* more whitespace fixes
* add changelog entry for 0.29.0
* Pushing new combined dist
Co-authored-by: Ishmeet Grewal <ishmeet@lightstep.com>
* Changelog for 0.29.0
* Whitespace fix
* 0.29.0
* allow specifying which auto-instrumented urls should have tracing headers (#237)
* allow specifying which auto-instrumented urls should have tracing headers
While the tracing headers are useful when sent to backends that expect, and
utilize them, automatic instrumentation is also useful for just tracking the
time and response status of requests to external services that aren't being
tracked. If such an external service has a strict policy on allowed headers the
automatically added headers will cause instrumented requests to error. So
instead of not getting any information from those URLs this commit adds the
ability to whitelist, and blacklist, the URLs that have tracing headers added to
them.
The new options are built off of the existing blacklist options and are:
- fetch_url_header_inclusion_patterns
- fetch_url_header_exclusion_patterns
- xhr_url_header_inclusion_patterns
- xhr_url_header_exclusion_patterns
* refactor _shouldTrace methods
* Adding babel spread library (#241)
* Adding babel spread library
* updating makefile
* Rebuild dist
* Update changelog for v0.30.0
* 0.30.0
* Fix node tracing opts bug (#242)
* Fix fetch (#5)
* fix request headers stuff wip
* refactor
* fix nodejs opts variable
* change in the options creation
* add changelog entry
* Fix types def to account for nodejs_url prefix (#245)
* Fix fetch (#5)
* fix request headers stuff wip
* refactor
* rename node_inclusion/exclusion patterns to node_url_exclusion/inclusion patterns in index.d.ts
Co-authored-by: Stephanie Baum <stephaniebaum@lightstep.com>
Co-authored-by: Isobel Redelmeier <iredelmeier@gmail.com>
Co-authored-by: Stephanie <stephanie@LS-MAC-041.local>
Co-authored-by: Drew Petersen <senofpeter@gmail.com>
Co-authored-by: Drew Petersen <kirbysayshi@gmail.com>
Co-authored-by: dm03514 <dm03514@gmail.com>
Co-authored-by: Ishmeet Grewal <ishmeet@lightstep.com>
Co-authored-by: Ishmeet Grewal <ishmeetsinghgrewal@gmail.com>
Co-authored-by: Mike Goldsmith <goldsmith.mike@gmail.com>
Co-authored-by: Thomas Crescenzi <trescenzi@gmail.com>
Co-authored-by: Jose Sabal <31045549+ODEit@users.noreply.github.com>
