One Hat Cyber Team

Your IP: 216.73.216.50
Server IP: 41.128.143.86
Server: Linux host.raqmix.cloud 6.8.0-1025-azure #30~22.04.1-Ubuntu SMP Wed Mar 12 15:28:20 UTC 2025 x86_64
Server Software: Apache
PHP Version: 8.3.23
Buat File | Buat Folder

View File Name : jest-resolver.js

module.exports = (path, options) => {
  // Call the defaultResolver, so we leverage its cache, error handling, etc.
  return options.defaultResolver(path, {
    ...options,
    // Use packageFilter to process parsed `package.json` before the resolution (see https://www.npmjs.com/package/resolve#resolveid-opts-cb)
    packageFilter: (pkg) => {
      // see https://github.com/microsoft/accessibility-insights-web/pull/5421#issuecomment-1109168149
      // see https://github.com/uuidjs/uuid/pull/616
      //
      // jest-environment-jsdom 28+ tries to use browser exports instead of default exports,
      // but uuid/react-colorful only offers an ESM browser export and not a CommonJS one. Jest does not yet
      // support ESM modules natively, so this causes a Jest error related to trying to parse
      // "export" syntax.
      //
      // This workaround prevents Jest from considering uuid/react-colorful's module-based exports at all;
      // it falls back to uuid's CommonJS+node "main" property.
      //
      // Once we're able to migrate our Jest config to ESM and a browser crypto
      // implementation is available for the browser+ESM version of uuid to use (eg, via
      // https://github.com/jsdom/jsdom/pull/3352 or a similar polyfill), this can go away.
      //
      // How to test if this is needed anymore:
      // - comment it out
      // - run `yarn test`
      // - if all the tests pass, it means the workaround is no longer needed
      if (pkg.name === 'uuid' || pkg.name === 'react-colorful') {
        delete pkg['exports'];
        delete pkg['module'];
      }
      // Jest + jsdom acts like a browser (i.e., it looks for "browser" imports
      // under pkg.exports), but msw knows that you're operating in a Node
      // environment:
      //
      // https://github.com/mswjs/msw/issues/1786#issuecomment-1782559851
      //
      // The MSW project's recommended workaround is to disable Jest's
      // customExportConditions completely, so no packages use their browser's
      // versions.  We'll instead clear export conditions only for MSW.
      //
      // Taken from https://github.com/mswjs/msw/issues/1786#issuecomment-1787730599
      if (pkg.name === 'msw') {
        delete pkg.exports['./node'].browser;
      }
      if (pkg.name === '@mswjs/interceptors') {
        delete pkg.exports;
      }
      return pkg;
    },
  });
};