Babel Config option
ts-jest
by default does NOT use Babel. But you may want to use it, especially if your code rely on Babel plugins to make some transformations. ts-jest
can call the BabelJest processor once TypeScript has transformed the source into JavaScript.
The option is babelConfig
and it works pretty much as the tsConfig
option, except that it is disabled by default. Here is the possible values it can take:
false
: the default, disables the use of Babeltrue
: enables Babel processing.ts-jest
will try to find a.babelrc
,.babelrc.js
file or ababel
section in thepackage.json
file of your project and use it as the config to pass tobabel-jest
processor.{ ... }
: inline Babel options. You can also set this to an empty object ({}
) so that the default Babel config file is not used.
Examples
Use default babelrc
file
// jest.config.js
module.exports = {
// [...]
globals: {
'ts-jest': {
babelConfig: true
}
}
};
// OR package.json
{
// [...]
"jest": {
"globals": {
"ts-jest": {
"babelConfig": true
}
}
}
}
Path to a balelrc
file
The path should be relative to the current working directory where you start Jest from. You can also use \<rootDir>
in the path, or use an absolute path (this last one is strongly not recommended).
// jest.config.js
module.exports = {
// [...]
globals: {
'ts-jest': {
babelConfig: 'babelrc.test.js'
}
}
};
// OR package.json
{
// [...]
"jest": {
"globals": {
"ts-jest": {
"babelConfig": "babelrc.test.js"
}
}
}
}
Inline compiler options
Refer to the Babel options to know what can be used there.
// jest.config.js
module.exports = {
// [...]
globals: {
'ts-jest': {
babelConfig: {
comments: false,
plugins: ['@babel/plugin-transform-for-of']
}
}
}
};
// OR package.json
{
// [...]
"jest": {
"globals": {
"ts-jest": {
"babelConfig": {
"comments": false,
"plugins": ["@babel/plugin-transform-for-of"]
}
}
}
}
}