microsoft / microsoft/TypeScript
Separate directories for map files
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 111k
- Forks
- 14.3k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 132
Description
Hi!
I find it rather odd that the option mapRoot exists without a corresponding option which outputs the map files to said directory. I have to manually move them after transpiling, which is annoying (AND keep the same directory structure).
Here is a SO question which is valid for my case aswell: https://stackoverflow.com/questions/43052200/can-i-place-webpack-source-maps-and-source-code-files-in-seprate-folders
I guess it's kinda related to: https://github.com/microsoft/TypeScript/issues/6723
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 tracing how mapRoot and source maps are handled during TypeScript transpilation. Define the expected behavior for a separate map-file output directory, including preservation of the directory structure, then identify the relevant compiler tests and update them to verify the generated paths.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- build-system, compilers
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100