TypeStrong / TypeStrong/ts-loader
Potential changes required for webpack 5
Open
Nobody has claimed this yet.
pinned
- Dominant language
- TypeScript
- Stars
- 3.5k
- Forks
- 439
- Avg merge
- 17h 17m
- Merged PRs (30d)
- 2
Description
There's some potential changes for ts-loader discussed here: https://github.com/zeit/ncc/issues/208
Opening this issue for traceability. If someone would like to implement suggestions from there that'd be awesome!
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
Read the linked zeit/ncc#208 discussion first to identify the webpack 5 changes proposed for ts-loader. No files or tests are named, so locate the affected loader entry points and relevant tests in this repository; done means the agreed suggestions are implemented and validated.
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
- Needs clarification
- Newbie friendliness
- 25/100