feat(resolve-extends): resolve pure-ESM presets (conventional-changelog v7/v9/v10)

[escapedcat]

Adopts the conventional-changelog family majors released 2026-06-26. Supersedes the three Renovate PRs (#4858, #4857, #4856).

Structured as four commits — the shared ESM resolver as a feat, then one fix per dependency bump:

• feat(resolve-extends): resolve pure-ESM parser presets
• fix: update dependency conventional-commits-parser to v7 (fix: update dependency conventional-commits-parser to v7 - autoclosed #4858)
• fix: update dependency conventional-changelog-conventionalcommits to v10 (fix: update dependency conventional-changelog-conventionalcommits to v10 - autoclosed #4857)
• fix: update dependency conventional-changelog-angular to v9 (fix: update dependency conventional-changelog-angular to v9 - autoclosed #4856)

Why the feat

conventional-changelog-angular@9 and conventional-changelog-conventionalcommits@10 are now pure ESM whose exports map declares only the import condition (no require/default/main). commitlint's CommonJS resolvers (require.resolve, resolve-from, resolve-pkg) fail with No "exports" main defined when resolving a string parser preset. @commitlint/resolve-extends now falls back to an ESM-aware node_modules walk only after CommonJS resolution fails — so resolution of normal packages is unchanged — with the equivalent fallback in the test bootstrap. Covered by new unit tests on synthetic exports-only manifests.

angular@9 typings

v9 ships its own types: createPreset() is typed {} and the named parser export was dropped (still present at runtime). The affected source/tests now read the options via createPreset().parser and drop the now-unused @ts-expect-error directives. The runtime in @commitlint/parse was already calling createPreset().parser, so only the cast/types changed.

User impact

Suitable for a minor release. commitlint only consumes these packages' parserOpts, never their writer/template side, and Node 22 was already required. The new capability is resolving pure-ESM parser presets; the one behavior change is the parser footer fix (conventional-changelog#1485) where BREAKING CHANGE notes no longer absorb trailing footer trailers.

Verification

• pnpm build (tsc -b --force, clean) ✅
• Full test suite: 1208 passed (incl. 3 new resolver tests) ✅
• oxlint ✅ · oxfmt --check ✅
• Manual CLI smoke test against @commitlint/config-conventional (valid / invalid / BREAKING CHANGE) ✅

🤖 Generated with Claude Code

[qodo-code-review]

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →

[greptile-apps]

Confidence Score: 5/5

Safe to merge; the new ESM resolver is a strict fallback that only activates after both CJS paths fail, leaving normal resolution behaviour unchanged.

The ESM fallback in resolveFrom is guarded by a try/catch and only fires when CommonJS resolution has already given up, so there is no regression risk for packages that CJS can already resolve. Root-entry resolution of pure-ESM packages is correct and covered by new unit tests. The one open gap — the subpath branch ignores the exports map for subpath entries — does not affect the declared targets.

@commitlint/resolve-extends/src/index.ts lines 86-93 (subpath resolution) if support for exports-mapped subpaths is ever needed.

Important Files Changed

Filename	Overview
@commitlint/resolve-extends/src/index.ts	Adds resolveExportsEntry and resolveEsmOnly as a CJS-fallback for pure-ESM packages; root-entry resolution is correct but the subpath branch skips the exports map and does a raw filesystem walk, which can miss non-trivial subpath mappings
@commitlint/resolve-extends/src/index.test.ts	Three new unit tests cover pure-ESM root resolution and fallback-to-main; the subpath test succeeds only because the file is at the naive path, not because the exports map was consulted
@commitlint/parse/src/index.ts	Removes @ts-expect-error and adds a runtime-safe cast to read `preset.parser
@commitlint/parse/src/index.test.ts	Introduces angularParserOpts() helper to access createPreset().parser with correct typings; removes four @ts-expect-error directives cleanly
@packages/test/src/npm.ts	Adds resolveModuleDir as a last-resort fallback that walks up from the current module file to find a package directory; handles pure-ESM packages that resolvePkg/require.resolve cannot locate
@commitlint/rules/src/references-empty.test.ts	Replaces @ts-expect-error with proper cast to { parser: ParserOptions } and switches from parserOpts to parser to match angular@9 API
@commitlint/rules/src/subject-exclamation-mark.test.ts	Same @ts-expect-error removal and parserOpts to parser field rename as references-empty.test.ts; clean change
@commitlint/config-conventional/package.json	Bumps conventional-changelog-conventionalcommits from ^9.2.0 to ^10.0.0
@commitlint/parse/package.json	Bumps conventional-changelog-angular to ^9.0.0 and conventional-commits-parser to ^7.0.0

_{Reviews (3): Last reviewed commit: "fix: update dependency conventional-chan..." | Re-trigger Greptile}