Package Exports
- dd-trace
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (dd-trace) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
dd-trace-js
JavaScript APM Tracer
Datadog APM tracing client for JavaScript.
Getting Started
For a basic product overview, check out our setup documentation.
For installation, configuration, and details about using the API, check out our API documentation.
For descriptions of terminology used in APM, take a look at the official documentation.
Development
Before contributing to this open source project, read our CONTRIBUTING.md.
Requirements
Since this project supports multiple Node versions, using a version manager such as nvm is recommended.
To get started once you have a Node version installed, run:
$ npm installTesting
Before running the tests, the data stores need to be running. The easiest way to start all of them is to use the provided docker-compose configuration:
$ docker-compose up -dTo run the unit tests, use:
$ npm testTo run the unit tests continuously in watch mode while developing, use:
$ npm run tddLinting
We use ESLint to make sure that new code is conform to our coding standards.
To run the linter, use:
$ npm run lintContinuous Integration
We rely on CircleCI 2.0 for our tests. If you want to test how the CI behaves locally, you can use the CircleCI Command Line Interface as described here: https://circleci.com/docs/2.0/local-jobs/
After installing the circleci CLI, simply run one of the following:
$ circleci build --job lint
$ circleci build --job build-node-4
$ circleci build --job build-node-6
$ circleci build --job build-node-8
$ circleci build --job build-node-latestBenchmarks
When two or more approaches must be compared, please write a benchmark
in the benchmark/index.js module so that we can keep track of the
most efficient algorithm. To run your benchmark, just:
$ npm run bench