qunitjs / eslint-plugin-qunit / 29263485396

95%

push

github

chore: export ./package.json (#691)

## Summary

\`require('eslint-plugin-qunit/package.json')\` currently throws
\`ERR_PACKAGE_PATH_NOT_EXPORTED\` because the exports map does not list
that subpath. Exporting it is a common ecosystem convention (tools that
resolve a plugin’s metadata by package name) and unblocks a follow-up
that replaces the \`index.js\` dist-vs-source
\`require(\"../package.json\")\` hack with a self-reference.

**Not included:** explicit \`types\` conditions on \`.\` /
\`./configs/*\`. Those are unnecessary today — TypeScript already finds
sibling \`.d.ts\` files next to the \`exports\` JS targets (\`attw\`
green; \`moduleResolution: node16\` scratch consumer type-checks both
entrypoints via sibling inference).

- Add \`\"./package.json\": \"./package.json\"\` to \`exports\`
- Leave existing \`.\` and \`./configs/*\` string targets unchanged
- Keep top-level \`main\` / \`types\`

## Test plan

- [x] \`require('eslint-plugin-qunit/package.json')\` succeeds via the
package name
- [ ] \`npm run build && npm pack\`

---------

Co-authored-by: Cursor <cursoragent@cursor.com>

824 of 925 branches covered (89.08%)

Branch coverage included in aggregate %.

5449 of 5661 relevant lines covered (96.26%)

406.36 hits per line