v1.0.2

Fixed

• The ./shared subpath now resolves under moduleResolution: node. A
  typesVersions map points the subpath at its .d.cts declarations, which is
  the only mechanism that resolution algorithm understands — it predates
  exports and ignores it entirely. Without this, a consumer whose tsconfig
  sets module: commonjs without an explicit moduleResolution (the default
  the Nest CLI scaffolds, which falls back to node) got
  error TS2307: Cannot find module '@bymax-one/nest-cache/shared' while the
  root entrypoint resolved fine. Runtime was never affected: Node reads
  exports, so require('@bymax-one/nest-cache/shared') always worked.

  This supersedes the note under 1.0.1 claiming the subpath was "not fixable
  without a directory shim" — that was wrong, typesVersions fixes it with no
  extra files in the tarball.

Changed

• check:exports now runs the strict attw profile. The --profile node16
  escape hatch existed only to ignore the failing node10 row, which no longer
  fails, so every entrypoint is now verified in every resolution mode.

v1.0.1

Fixed

• CommonJS consumers no longer receive ESM type declarations. Both subpaths
  now declare types per condition, so require() resolves to the .d.cts
  declarations that match the .cjs runtime. Previously a single types entry
  pointed at the .d.ts files, which — with "type": "module" — TypeScript
  reads as ESM, so a project on moduleResolution: node16 / nodenext
  importing from CommonJS got declarations for the wrong module format.
• Added top-level main, module and types so the root entrypoint also
  resolves under the legacy moduleResolution: node algorithm. The ./shared
  subpath remains unresolvable in that mode, which is inherent to subpath
  exports and not fixable without a directory shim.
• Exposed ./package.json through the exports map. Reading it previously
  failed with ERR_PACKAGE_PATH_NOT_EXPORTED, which breaks tooling that
  inspects an installed package's manifest.

Added

• pnpm check:exports (@arethetypeswrong/cli) — packs the tarball and
  resolves every entrypoint the way each module resolution mode would. Wired
  into CI and into the release-shape gates, since the type-level API tests
  compile src and therefore cannot catch a broken exports map.