Modularization, NPM
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 29
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
Two options for modularization. One is to split each class into its own module, like `math-matrix4` etc. Another is to "lock" the folder structure and encourage people to use `require('vecmath/lib/Matrix4')` if they need the granularity of a single class.
The former is probably a better solution for the long run.
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
The issue presents two modularization approaches but names no files, tests, or entry points. Start by inspecting the package structure and NPM configuration, then compare the two proposed layouts; done would require a decided modularization strategy and corresponding package structure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100