Instrument your JS code via commmand-line
The configuration is done as part of the `package.json:
Sets the entry file, normally the first file to be loaded. The basic configuration will be included in the output file.
The files to be transpiled given in an array of object with these three keys
The current working directory to take the files from
The source files, globbing is possible here
The directory to write the files to (respectant to their path from the cwd directory)
The output file to write the transformed entry file to.
An array of objects containing the configuration for the advices. Advices are the foundation of this library, as they collect the data to be monitored. They may be found on npm.
Boolean flag that allows or disallows ECMAScript 6 code to be instrumented.
Writing your own Advice
- As you (most likely) need some form of configuration or automated instrumentation to be used in this cli you need to add your package to this
Writer work in a separate thread and send the data to the destination you want. They may be found on npm.
require is not a function / undefined
The problem is that you are currently not using a build tool which
- inlines the required JS files or
- provides a require function in both the normal and the worker thread
To solve this, please use browserify in your build chain.
MIT © Daniel Schmidt