DocumentationGrafana k6Using k6JavaScript and TypeScript mode
Open source

JavaScript and TypeScript compatibility mode

You can write k6 scripts in various ECMAScript versions:

  • ES6+ JavaScript with ES modules (ESM).
  • ES6+ JavaScript with CommonJS modules.

k6 supports both module types and most ES6+ features in all k6 execution modes: local, distributed, and cloud.

To enable ES module support, k6 uses Babel internally to transform ESM to CommonJS. The process is as follows:

Babel transformation in k6

Additionally, k6 also has experimental support for esbuild, to transpile TypeScript (TS) code and to support most ES6+ features.

Some users prefer to bundle their test code outside k6. For this reason, k6 offers three JavaScript compatibility modes:

When running tests, you can change the mode by using the --compatibility-mode option:

EnvCLICode / Config fileDefault

Extended mode

By default, k6 uses the --compatibility-mode=extended mode:

$ k6 run script.js

As illustrated in the previous diagram, if k6 detects unsupported ES+ features while parsing the test script, it then transforms the script with Babel to polyfill the unsupported features.

Currently, the k6 Babel transformation only adds ESM support and sets global (node’s global variable) with the value of globalThis.

Experimental enhanced mode

$ k6 run --compatibility-mode=experimental_enhanced script.ts
$ K6_COMPATIBILITY_MODE=experimental_enhanced k6 run script.ts

The experimental enhanced mode is similar to the extended mode, but it uses esbuild instead of Babel to transpile TypeScript (TS) code and to support most ES6+ features.

TypeScript support is partial as it removes the type information but doesn’t provide type safety.

Base mode

$ k6 run --compatibility-mode=base script.js
$ K6_COMPATIBILITY_MODE=base k6 run script.js

The base mode omits the Babel transformation step, supporting only ES5.1+ code. You may want to enable this mode if your scripts are already written using only ES5.1 features or were previously transformed by Babel.

Generally, this mode is not recommended as it offers minor benefits in reducing startup time.

CommonJS Example

const http = require('k6/http');
const k6 = require('k6');

module.exports.options = {
  vus: 10,
  duration: '30s',

module.exports.default = function () {

⚠️ About require()

Note that require() is a custom k6 implementation of module loading, which doesn’t behave in the same way as the require() call in Node.js. Specifically, it only handles loading of built-in k6 modules, scripts on the local filesystem, and remote scripts over HTTP(S), but it does not support the Node.js module resolution algorithm.

Bundling with Babel outside of k6

The examples below demonstrate the use of Babel with bundlers like Webpack and Rollup:

Read more

  • Native ESM support: GitHub issue for native ESM support in k6. This feature aims to eliminate the Babel transformation step within k6.
  • Running large tests: Optimize k6 for better performance.
  • k6 Modules: Different options to import modules in k6.
  • k6 Archive Command: The k6 archive command bundles all k6 test dependencies into a tar file, which can then be used for execution. It may also reduce the execution startup time.