Module resolution
Open
Nobody has claimed this yet.
benchmark-needed
- Dominant language
- Shell
- Stars
- 399
- Forks
- 11
- Avg merge
- 29m
- Merged PRs (30d)
- 1
Description
Following the tweet by Marvin - and the subsequent article we should see how we can take that feedback into account and see how we can improve the performances around module resolution
- stacktrace /
throwIfNoEntryinfs.stat - cache when accessing file
- file extension
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 with Marvin's linked article and the three concerns listed in the issue: fs.stat stacktrace/throwIfNoEntry, caching file access, and file extensions. No files, tests, or entry points are named, so first map the module-resolution path and identify relevant benchmarks. Done requires a scoped improvement with measurable performance results and coverage for the selected concern.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- performance, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100