As both ./min and . points to the same type definition file, sometimes TypeScript will resolve the type definition entry to the ./min key as it appears first.
While this is not incorrect behavior, it breaks compatibility with older build environments that do not support the exports field. (e.g. TypeScript with moduleResolution: "node" instead of bundler or node16), as the ./min entry is only available through the exports field.
As both
./min
and.
points to the same type definition file, sometimes TypeScript will resolve the type definition entry to the./min
key as it appears first.https://github.com/microsoft/TypeScript/issues/56290#issuecomment-1792883895
While this is not incorrect behavior, it breaks compatibility with older build environments that do not support the
exports
field. (e.g. TypeScript withmoduleResolution: "node"
instead ofbundler
ornode16
), as the./min
entry is only available through theexports
field.Some Vue.js users are experiencing this issue: https://github.com/vuejs/core/issues/9521