Implementation help
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 261
- Forks
- 31
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 4
Description
Hi, i have been working on a fork of browserify and have been wanting to implement a worker pool for transforms using something like this so that it can keep up with esbuild. here is a repo with the bundler in tools/omnify/bundler. The speed increase (compared to browserify) is mostly coming from replacing acorn/detective with regex. https://github.com/jeremy-coleman/esbuild-vs-omnify-r3f . I think this would be a really good dogfood project for this lib and node streams in general. If you think it’d be interesting and would like to brainstorm , lmk.
Contributor guide
No contributing guide indexed for this repository
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 reviewing the thread-stream repository and the linked tools/omnify/bundler implementation, then examine how Node.js streams and transforms are used. The issue proposes a worker pool but does not define its interface, scope, or completion criteria, so the desired behavior would need to be clarified before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- backend, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100