[Feature Request] melonJS lib as npm dependency #26
Comments
Unfortunately the biggest problem with using npm with our current melonJS source code is that melonJS isn't modular at the moment. It needs to be built into one giant concatenated file. Our build process tries (tried? what happened to it?) address this by building the giant files and committing them off-branch with tags. The idea is that a package manager like npm or bower can fetch the commit which contains the pre-built files. I think it's not currently working this way, though. I agree, it would be a much cleaner implementation. The build infrastructure just needs a little work to get there. |
I think it would work out of the box if the That script is called everytime the package is installed, so the main file specified here will be there once the package is installed. Even if it's not modular yet, I think it's better than nothing :) |
I see you are making MelonJS modular in v.6.0.0 melonjs/melonJS#915 |
yes ! but "converting" the whole source code it's a long and tedious task to be honest :) |
done a while ago now, but the boilerplate will now use the latest melonJS version out of jsDeliver: but if you need/prefer NPM it's also properly available there since version 7.0 : |
I would like to avoid including the melonJS library source code directly in my project repositories and I think that the proper way to do that would be to require MelonJS and MelonJS plugins as npm dependencies in the
package.json
, but as far as I know there is no official npm package for MelonJS / MelonJS plugins, right? You may need to register them I guess.melonjs
andmelonjs-plugins
names are available in the npm registry.For the
Gruntfile.js
and theindex.html
I would just reference the js files fromnode_modules
instead oflib
.What do you think?
The text was updated successfully, but these errors were encountered: