const nxPreset = require('@nx/jest/preset').default;

// Dependencies that ship ESM-only builds Jest cannot `require`. A suite that reaches one of them
// fails to LOAD rather than failing an assertion — Jest reports that as a suite error, which reads
// like "no tests here" instead of "coverage is zero", so the tests silently stop running.
//
// This list used to live in `packages/core/jest.config.ts` (with a copy in integration-zapier), so
// the other projects that inherit this preset started without it. That is why the videos,
// job-proposal and wakatime service/controller specs — whose testing modules load `@gauzy/core` —
// failed to load. It lives here so a project gets it by inheriting the preset. Keep it to packages
// actually reached by a spec, and add whole dependency subtrees (walk for `"type": "module"`) rather
// than one package per failing run:
//   sanitize-html + its parser stack -> rich-html-sanitizer / public-html-sanitizer
//   uuid                             -> time-tracking + email-check suites, and any spec that loads
//                                       `@gauzy/core` for real
//   camelcase                        -> time-tracking suites
//   @faker-js/faker                  -> reached through the entity graph (core/seeds)
//   @nestjs/axios                    -> ships a raw `index.ts` that re-exports `./dist`
//   @datorama/akita, @ngneat/*       -> the Angular state stores (ui-core and every UI plugin reach them)
//   lodash-es                        -> Angular UI code, and angular2-smart-table's .mjs bundle
//   d3-*, internmap                  -> @swimlane/ngx-charts (desktop-ui-lib's recap module, which the
//                                       desktop apps' shells load through the library's entry point)
// plus every `.mjs` file: Angular and its ecosystem ship ESM-only `fesm2022/*.mjs` bundles, which the
// Angular projects compile with jest-preset-angular. A Node project only pays for that alternative
// when one of its specs actually reaches an `.mjs` file, which would otherwise fail to load anyway.
// Listing packages, rather than transforming all of node_modules, bounds the transform work. The
// `(?:.*/)?` prefix also matches nested copies and same-named directories inside other packages
// (e.g. `@smithy/uuid`); that only costs some transform time.
//
// Things this depends on that are easy to break from elsewhere:
//   - ts-jest (>= 29.3.2; pinned at 29.4.6) compiles a `.js` file under `node_modules` to CommonJS
//     whenever Jest hands it over, whatever `allowJs` says — so a project needs nothing else for this
//     list to take effect. `allowJs` only matters for repo-local `.js` files.
//   - A project that sets its own `transformIgnorePatterns` REPLACES this one rather than adding to
//     it. The Angular projects used to do exactly that with `['node_modules/(?!.*\\.mjs$)']` — the
//     `.mjs` exception and nothing else — so akita, @ngneat/effects and lodash-es never got
//     transformed there and ~22 Angular suites failed to load. They now inherit this list, which is
//     why the `.mjs` alternative lives here. Still defining their own: `docs` (a narrower list),
//     `integration-zapier` (a copy of this list, which has to track it) and the three React
//     projects (`.mjs` only, which is all they need today).
//   - `@gauzy/*` is deliberately absent, and adding it would do nothing. Jest resolves workspace
//     packages to their real source path (`packages/<pkg>/src/index.ts`), which has no
//     `node_modules/` segment, so this pattern is never consulted for them.
const transformIgnorePatterns = [
	String.raw`node_modules/(?!.*\.mjs$|(?:.*/)?(sanitize-html|htmlparser2|domelementtype|domhandler|domutils|dom-serializer|entities|nanoid|parse-srcset|uuid|camelcase|@faker-js|@nestjs/axios|@datorama|@ngneat|lodash-es|d3-[a-z-]+|internmap)/)`
];

module.exports = {
	...nxPreset,
	transformIgnorePatterns,
	// The Nx resolver plus one rule: a Jest project sees ONE copy of `@angular/*`. See the file.
	resolver: require.resolve('./jest.resolver.js'),
	// ngx-daterangepicker-material (ui-core's date-range selector) imports `dayjs/esm` and its plugins
	// from an `.mjs` bundle. Transforming that ESM tree is not enough: an `.mjs` importer gets Node's
	// default-import semantics (the whole module object), so `dayjs.extend` came out undefined and
	// every suite reaching the selector failed to load. The package's CommonJS build is the same code
	// with `module.exports = dayjs`, which is what those semantics expect. (Jest merges a preset's
	// `moduleNameMapper` with a project's own.)
	moduleNameMapper: {
		'^dayjs/esm$': 'dayjs',
		'^dayjs/esm/(.*)$': 'dayjs/$1'
	},
	// `moment` and `randomcolor` load with both default and namespace imports, as the bundlers allow.
	// Jest CONCATENATES a preset's `setupFiles` with a project's own, so no project loses it.
	setupFiles: [require.resolve('./jest.interop.js')]
};