Fixing TypeScript type definitions for image components #3980
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.
closes #3967
Changes
Typescript isn't properly inferring types from
@astrojs/image
unless imported from@astrojs/image/components
. Reverting the package to import from the components directory for now until we find a clear best practices for Astro component packagesAlternatives tried
I got close using
typesVersions
in the integration'spackage.json
, but TypeScript then ran into an error that the imported<Image />
component couldn't be used because it is exported withexport type
.Future work
Find the right solution here to allow package authors to easily use named exports for Astro components, with full TypeScript support
Testing
Existing tests should pass
Docs
README examples updated