TypeStrong / TypeStrong/ts-loader
Use webpack's inputFileSystem for the resolver, instead of a seperately cached version
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
Use webpack's inputFileSystem for the resolver, instead of a seperately cached version
Actual Behaviour
Uses seperately cached version
See #1405 for prior art and inspiration cc @alexander-akait
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
Review issue #1405 for the prior art and inspect how the resolver currently uses its separately cached filesystem. Trace the webpack loader's inputFileSystem integration and verify that the resolver uses it instead; the change is done when the separate cached version is no longer used.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, webpack
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100