fix: correct jest-either type exports

[YfengJ]

Summary

• point @pacote/jest-either package types metadata at the generated ESM declaration file
• add an exports["."].types condition so TypeScript NodeNext consumers can resolve the root package types

Why

The published @pacote/jest-either@6.0.1 package declares types: lib/index.d.ts, but the npm tarball contains lib/esm/index.d.ts and lib/cjs/index.d.ts instead. Because the package also defines exports, TypeScript NodeNext consumers cannot resolve the root package declarations without an explicit types export condition.

Validation

• COREPACK_ENABLE_PROJECT_SPEC=0 corepack pnpm exec biome check package.json packages/jest-either/package.json
• COREPACK_ENABLE_PROJECT_SPEC=0 corepack pnpm --filter @pacote/jest-either... build
• COREPACK_ENABLE_PROJECT_SPEC=0 corepack pnpm vitest run packages/jest-either/test
• COREPACK_ENABLE_PROJECT_SPEC=0 corepack pnpm lint — exits 0; reports two existing unused-suppression warnings in packages/error/src/index.ts
• npm pack --dry-run --ignore-scripts --json ./packages/jest-either
• packed packages/jest-either, installed it into a temporary NodeNext TypeScript consumer, and verified import matchers, * as named from "@pacote/jest-either" compiles with tsc --noEmit
• git diff --check

[goblindegook]

Thanks for the patch but a script to validate the format of a declarative file such as package.json should not be necessary. Happy to merge if you remove this.

[YfengJ]

Thanks for reviewing. I removed the package entrypoint verification script and the root test:package hook, leaving only the @pacote/jest-either package metadata fix. I also updated the PR description with the current validation commands.

[goblindegook]

Thanks!

[YfengJ]

Thanks for the review and for merging this. I appreciate the guidance on keeping the package metadata fix focused.