TypeStrong / TypeStrong/ts-loader
feat: support options when getCustomTransformers is a path string
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
{
loader: require.resolve('ts-loader'),
options: {
getCustomTransformers: {
path: string,
options: {[k:string]: any}
},
},
},
Actual Behaviour
{
loader: require.resolve('ts-loader'),
options: {
getCustomTransformers: string
}
},
Steps to Reproduce the Problem
Location of a Minimal Repository that Demonstrates the Issue.
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 ts-loader handles the getCustomTransformers option when it is a path string. Support the shown object form with path and options while preserving the existing string form; done means both forms are accepted as TypeScript loader options.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, webpack
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100