microsoft / microsoft/TypeScript
intellisense typeroots for jsconfig.json
Open
Nobody has claimed this yet.
Experience Enhancement
Suggestion
- Dominant language
- Go
- Stars
- 111k
- Forks
- 14.3k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 132
Description
Suggestion
Add the typeRoots property for jsconfig.json like tsconfig.json
Use Cases
In an Asp.net Core project , there are no intellisence for view.cshtml file's <script> when my type definition file put in wwwroot/@typings
Examples
/aspnetcoreproject
| wwwroot
|@typings
|tsconfig.json
|Views
|Home
|index.cshtml (can not find the type definition files)
|jsconfig.json
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
Compare how jsconfig.json and tsconfig.json handle configuration properties, then trace the existing typeRoots handling. Verify the change against the Asp.net Core example so type definitions under wwwroot/@typings are available to script code in index.cshtml.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100