Add typesVersions for legacy TypeScript moduleResolution support #7
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
typesVersionsfield to package.json to support legacy TypeScript configurations/react,/core) for users withmoduleResolution: "node"Problem
Users with older TypeScript setups reported needing to change their
tsconfig.jsontomoduleResolution: "bundler"to use this SDK. This broke other imports in their projects.The root cause: TypeScript's
moduleResolution: "node"doesn't read theexportsfield in package.json, so it couldn't resolve types for subpath imports like@hygraph/preview-sdk/react.Solution
Added
typesVersionsas a fallback for legacy TypeScript resolution:This is safe because TypeScript prioritizes exports over typesVersions when both are present - modern setups are unaffected.
Test Plan