max-mapper / max-mapper/voxel-builder
Publish on npm ?
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 150
- Forks
- 50
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
I am probably going to use voxel-painter as a base for a project where I will need to extend it, so I wanted to know if you had any plans on publishing it as a module.
The best would be to be able to create "plugins" à la voxel-engine (to use informations from the module, or trigger actions on some hooks, stuffs like that).
If this is not something you're planning that's not a big deal as I can hack it to make it my own, but it would be better to use it as a module to benefit from bug fixes, improvements and such. Also I realize it could be a lot of work as it's completely linked to the markup as it is, but I would be glad to work on it if needed.
Thanks
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
Review the current voxel-painter structure and its coupling to markup before deciding whether npm publication and plugin support are feasible. Define the module boundary, the information and hooks plugins would expose, and the scope of a publishable package; the issue is complete when that direction is agreed and documented.
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
- 25/100