Jest not picking latest plugin from babel.config.js

I have my own babel plugin mentioned in babel.config.js and when I change the plugin, jest doesn’t pick the updated plugin code and breaks tests. When I run npx jest --no-cache, updated changes are picked up.

I do not want to run with --no-cache everytime I update the plugin.

I am curious to know how jest picks the latest babel plugins, when they are updated in npm artifactory?

I have mentioned my plugin in babel.config.js as:

module.exports = function (api) {
  api.cache(true);

  const presets = ["@babel/preset-env", "@babel/preset-react"];
  const plugins = [
    "@babel/plugin-syntax-dynamic-import",
    "@babel/plugin-proposal-class-properties",
    "@babel/plugin-transform-runtime",
    ["module:@babel-plugin-dynamic-import-override", {
      options: someOptions
    }]
  ];

  return {
    presets,
    plugins
  };
}

Also, what changes do I make to my jest.config.js to make it pick the latest plugins?

[SimenB]

We don’t, and we won’t add it. It’s not a common use case to change the implementation of babel plugins while running tests, and we already have a way too big API. If you want you can extend babel-jest and add some sort of env variable to the getCacheKey function.

import { createTransformer } from 'babel-jest';

const transformer = createTransformer();

export = {
  ...transformer,
  getCacheKey(...args) {
    const key = transformer.getCacheKey(...args);

    return key + process.env.THING_I_CARE_ABOUT;
  },
};

https://jestjs.io/docs/en/configuration#transform-object-string-pathtotransformer-pathtotransformer-object

[github-actions[bot]]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.