voxel / voxel-sfx

sound effects (voxel.js plugin)
3 stars 1 forks source link

Development Workflow #5

Open z3t0 opened 9 years ago

z3t0 commented 9 years ago

I was wondering what the development workflow for developing plugins is. Do you create the plugins and work on them in a different directory of do you work inside node_modules? This is assuming that the plugin is being accessed from the github repository directly and not npm install, as that would be impractical for very commit.

deathcap commented 9 years ago

I make extensive use of npm link: http://blog.nodejs.org/2011/04/06/npm-1-0-link/ - very convenient

sudo npm link in the plugin directory (I keep it all at one level in ~/games/voxeljs, not directly editing node_modules), then npm link voxel-foo in the application directory. This will setup symlinks so the node_modules dependency directly points to your local work-in-progress version. (The downside is then you have to be careful to keep the package.json version correct, since it'll use whatever is in your local copy, regardless of the package.json dependency version which can get out of sync)

z3t0 commented 9 years ago

@deathcap Thanks for that! I have been using it today and also find it super useful!

Note: lets keep this issue open until I add this to the docs

z3t0 commented 9 years ago

@deathcap do we have a wishlist somewhere for the plugins we need to develop? looking for somewhere to start

deathcap commented 9 years ago

https://github.com/deathcap/voxel-ideas/issues

z3t0 commented 9 years ago

Ok thanks, I'll see what I can do