Fix TypeScript resolution for @magic-ext/* packages when using modern module resolution (node16 etc) #670
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.
📦 Pull Request
This PR updates the
package.json
files for all of the@magic-ext
packages (apart from aptos and solana, which already had this change applied).This is essentially the same change that has already been applied in #517 by @octave08 (why wasn't this done for all packages?) and proposed in #626
✅ Fixed Issues
Fixes #669
🚨 Test instructions
Create a new TypeScript web app that uses
node16
ornodenext
module resolution, try to import these packages, TypeScript should be able to perform type checking based on the types of the imported objects.Please only add one label:
patch
: Bug Fix?minor
: New Feature?major
: Breaking Change?skip-release
: It's unnecessary to publish this change.