Npm support?

[sebastiendan]

Hi thanks for your great great library!

Any chance to put it on npm registry?

Thanks!

[kittykatattack]

Sorry, there won't be any NPM support ... unless someone out there want to take it on as a project?
If you do, drop us a line in this thread and we'll figure it out 😄

[mattlima]

I think npm support would be a great next step for Hexi as it evolved towards v1. There are, however, some implications for the codebase, particularly w/r/t variable scope. I've been working on a Gulp compilation pipeline for the lib and I see that sound.js for example uses this to refer to the global scope. I'd want to turn each module into an npm package and then have core.js require them (and Pixi as well, we can lock the pixi version package.json). Having a modules.js would seem like overkill in this case, but I can see us keeping a 'fat' hexi file as part of the distribution which would load pixi, the modules, and core. Maybe we can take a look after the Gulp pipeline stuff is done?

[kittykatattack]

I totally agree!

[flozero]

Hello all i am trying to use all of the concept that propose exi by patching every modules on hexi with a complete npm interaction and es6 basic support and using the new pixi version

But my knowledge is just at the beginning. If some people want to help me to understand i will be capable to create a real npm bundler