TypeStrong / TypeStrong/ts-loader
Memory consuption problem
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 3.5k
- Forks
- 439
- Avg merge
- 17h 17m
- Merged PRs (30d)
- 2
Description
We are using ts-loader with a webpack configuration on our projects. On last days we monitor that our applications consume very high level memory.
Operation system: Windows 10
Expected Behaviour
Memory usage must be normal level.
Actual Behaviour
Every webpack application uses more than 1-1.5 GB memory
Steps to Reproduce the Problem
Use ts-loader with webpack with a few helper plugin like TsconfigPathsPlugin, Dotenv, DeadCodePlugin, HtmlWebpackPlugin
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
No minimal repository, files, or tests are provided. Start by reproducing the reported memory usage on Windows 10 with ts-loader, webpack, and the listed plugins, then isolate which configuration or plugin causes usage above 1–1.5 GB. Done means identifying a reproducible cause and documenting the affected setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, webpack
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100