trekhleb / trekhleb/javascript-algorithms
Suggestion: ship production ready build to npm
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 197k
- Forks
- 31k
- PR merge metrics
- No merged PRs in 30d
Description
Hey,
I noticed that the current version deployed on npm (i.e. https://www.npmjs.com/package/javascript-algorithms-and-data-structures) is more or less a mirror of the source code here. javascript-algorithms is really awesome and someone might want to use it as an external library on production (e.g. a web app or node app). Unfortunately, the use of ES modules, complicates things a bit.
May I suggest:
- Transpiling code to ES2015, using CommonJS instead of ES modules;
- Removing redundant source code (e.g. comments, README, etc) to reduce package size.
I'd be more that willing to provide a PR using rollup + babel.
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 files or tests are named. Start by reviewing the current npm package and how the repository builds its ES module source; compare the proposed Rollup and Babel approach with the existing package contents. Done means a production-ready CommonJS/ES2015 package is published without redundant source or documentation files.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- babel, javascript, rollup
- Domain
- build-system, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100