TypeStrong / TypeStrong/ts-loader
Enabling `enhanced-resolve` Causes Errors
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
Running webpack using ts-loader with enhanced-resolve enabled causes errors as described in #1504 and #1505.
Actual Behaviour
webpack should still run properly with ts-loader.
Steps to Reproduce the Problem
- Install
ts-loader@9.4.0 - Install
spica - Import
setTimeoutfromspica/global - Try to compile the module using
webpackwithts-loader - Take note that the compilation fails
Location of a Minimal Repository that Demonstrates the Issue.
- https://github.com/falsandtru/pjax-api/tree/76ad3769e23497a15817914a92787089c5dfa8cc
- https://github.com/falsandtru/clientchannel/tree/ec42cd2d3df396c6ee9f5cc82465cd6898174fda
Thanks a lot to @falsandtru for providing the demonstrations!
This issue is related to #1506, #1504 and #1505
The error has been introduced in #1503
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 reproducing the failure with ts-loader@9.4.0, enhanced-resolve, spica, and the linked pjax-api or clientchannel repositories. Read the error details in issues #1504 and #1505 and the change from #1503; done means webpack compiles the module successfully with ts-loader and enhanced-resolve enabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, webpack
- Domain
- build-system, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100