TypeStrong / TypeStrong/ts-loader
Add native support for tsconfig `compilerOptions.paths`
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 3.5k
- Forks
- 439
- Avg merge
- 17h 17m
- Merged PRs (30d)
- 2
Description
Expected Behaviour
Output js should contain transpiled import paths according to compilerOptions.paths config. This behaviour will be in sync with how babel handles that with its plugin and also more expected then current behaviour.
Actual Behaviour
Import paths not replaced and additional plugin is needed to replace them
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 locating how ts-loader handles TypeScript module resolution and compare that behavior with compilerOptions.paths and the linked Babel plugin. Done means emitted JavaScript imports follow the configured paths without requiring an additional plugin, with tests covering the behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, webpack
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100