microsoft / microsoft/nodejstools
tsconfig.json issues with outDir / rootDir
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 1.8k
- Forks
- 355
- PR merge metrics
- No merged PRs in 30d
Description
Node Tools is not aware of the location of the compiler output when either of the following is specified:
- outdir
- outfile
- rootdir
This causes a number of issues, captured in the following issues:
#1793
#1243
#1241
#1087
The solution is 2 fold, we need the TypeScript to expose an API, which allows us to determine the output path for a specific .ts file in the case of a tsconfig.json file, and we need to query that API when debugging, detecting changes for rebuild, and locating unit tests.
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 tsconfig.json options listed: outDir, outFile, and rootDir, then investigate the TypeScript API needed to determine a specific .ts file's output path. Trace how Node Tools uses output locations for debugging, rebuild change detection, and unit-test discovery. Done means those workflows use the configured compiler output location; related context is in issues #1793, #1243, #1241, and #1087.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- build-system, devtools, testing-qa
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100