Since the template itself is only going to include a small number of defaults, game developers should easily be able to pull in whatever other libraries they want.
This user story only covers libraries which execute in the browser X Libraries which are normally loaded by script tag should be supported X AMD libraries should be supported.
Users should not be asked questions that can't be easily answered (depends on https://github.com/volojs/volo/issues/29)
Libraries should be installed in the appropriate spot in the project hierarchy (depends on https://github.com/volojs/volo/issues/29)
Libraries should not be automatically loaded; that's left up to the developer
Libraries should be tracked in package.json
Should come up with a list of popular game libraries, ensure they work (Three.js, CubicVR.js, Gladius, see github engine list for more)
Volo uses github as registry for possible libraries, which is great, since that's where most open source things live these days.
This closes out most of https://github.com/gladiusjs/html5-game-template-old/issues/5, albeit without automated tests. The work of getting a minimally viable set of compatible libraries will happen in a new git issue.
The issue that this mostly closes out:
Since the template itself is only going to include a small number of defaults, game developers should easily be able to pull in whatever other libraries they want.
Volo uses github as registry for possible libraries, which is great, since that's where most open source things live these days.