JavaScript instrumentation
The Antithesis platform can automatically instrument JavaScript code by performing a source transformation after you’ve sent it to us. No changes to your source code or build system are required. Our instrumentor assumes by default that you are using NodeJS as your runtime — contact us if you’d like to use a different runtime. We do not support instrumenting JavaScript code that runs in a browser.NodeJS
Place directories, files, or symlinks to the code you want instrumented or cataloged in the directory/opt/antithesis/catalog/ within your container image. Antithesis will follow all symlinks while resolving the path to the cataloging directory.
However, it will follow only one symlink deep into each item placed within /opt/antithesis/catalog/. That is, you should not symlink to a symlink.
Example cataloging directory:
dotnet_file.dllpython_script.pymain.jar
my_other.jar- this will be ignored as we already encountered one symlink when traversing down fromopt/antithesis/catalog/more_files.
node_modules and recursively instrument all of the code within said directories; however, it will by default exclude everything in node_modules and some standard configuration files that happen to be implemented as JavaScript (for instance eslint.config.js). It follows that vendored dependencies will be instrumented by default.
The instrumentor will, by default, act upon every language it supports in the cataloging directory: (Java , Python, JavaScript, .NET), not just JavaScript.
require by default, but can be configured to support import — email us at support@antithesis.com and we’ll flip the setting for your account.