fix: support autoimports typeFrom property for declaration gen
#3670
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@8ctavio is attempting to deploy a commit to the Nitro Team on Vercel. A member of the Team first needs to authorize it. |
typeFrom property for declaration file generationtypeFrom property for declaration gen
commit: |
pi0
pushed a commit
that referenced
this pull request
Oct 23, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
🔗 Linked issue
#3669
❓ Type of change
📚 Description
Inside the writeTypes function, an import's path specifier is now retrieved from
_import.typeFrom || _import.frominstead of only_import.from, so thattypeFromis used for generated declaration files, if provided.📝 Checklist