Add named export to @commitlint/parse

[lachlancollins]

Description

This PR adds a named export alongside a default export, which fixes imports in an ESM context.

Motivation and Context

• When working on chore: Migrate scripts to ESM TanStack/query#5486, I came the following issue trying to run scripts/publish.mjs: TypeError: parseCommit is not a function
• The script uses import parseCommit from '@commitlint/parse' then later calls const parsed = await parseCommit(d.subject), and no typechecking errors are raised (using @ts-check)
• However, if I instead call const parsed = await parseCommit.default(d.subject) I get a type error, but the script works without issues (see here)
• This seems to be some weird ESM/CJS incompatibility (this might be relevant?), which can be solved by using a named export

Usage examples

CJS: const parse = require('@commitlint/parse')
ESM: import { parse } from '@commitlint/parse'

How Has This Been Tested?

I tried the build output in the Tanstack Query codebase and it worked 👍

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.

[escapedcat]

Thanks @lachlancollins ! Will push a new release soonish.

[escapedcat]

Damnit, didn't check the commit message :D Will update it.

[escapedcat]

https://github.com/conventional-changelog/commitlint/releases/tag/v17.6.5