Fixed
-
The
./sharedsubpath now resolves undermoduleResolution: node. A
typesVersionsmap points the subpath at its.d.ctsdeclarations, which is
the only mechanism that resolution algorithm understands — it predates
exportsand ignores it entirely. Without this, a consumer whose tsconfig
setsmodule: commonjswithout an explicitmoduleResolution(the default
the Nest CLI scaffolds, which falls back tonode) got
error TS2307: Cannot find module '@bymax-one/nest-cache/shared'while the
root entrypoint resolved fine. Runtime was never affected: Node reads
exports, sorequire('@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,typesVersionsfixes it with no
extra files in the tarball.
Changed
check:exportsnow runs the strictattwprofile. The--profile node16
escape hatch existed only to ignore the failingnode10row, which no longer
fails, so every entrypoint is now verified in every resolution mode.