microsoft / microsoft/TypeScript
Remote declaration file
Open
Nobody has claimed this yet.
Awaiting More Feedback
Suggestion
- Dominant language
- Go
- Stars
- 111k
- Forks
- 14.3k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 132
Description
Search Terms
- Remote Reference
- Remote Declaration
- Declaration URL
Suggestion
Being able to reference .d.ts files from a remote location
Use Cases
Reference .d.ts files which can match with import "http://example.com/Component1"
Examples
/// <referance path="http://example.com/Definitions/Component1" />
import "http://example.com/Component1"
Checklist
My suggestion meets these guidelines:
- This wouldn't be a breaking change in existing TypeScript/JavaScript code
- This wouldn't change the runtime behavior of existing JavaScript code
- This could be implemented without emitting different JS based on the types of the expressions
- This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
- This feature would agree with the rest of TypeScript's Design Goals.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the suggestion, its remote-reference use case, and the linked TypeScript Design Goals. Determine how remote .d.ts files would match HTTP imports while preserving existing JavaScript runtime behavior and emitted output. Done means the proposal has an agreed implementation scope and acceptance criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100