Publish to npm
englercj opened this issue · comments
DO IT
I think that this issue is related to pixijs/pixijs#307
In what way?
Before publishing this package to npm I think you should list pixi.js as a dependency in package.json but pixi.js can't be listed as a dependency as soon as pixijs/pixijs#307 is open.
I don't pull pixi in via package manager, I pull the compiled file into my vendor folder; so it isn't an npm dependency. Npm would report errors if I placed it there.
Ok then...
I have released grapefruit into npm and bower. Enjoy!
@englercj Did you mean pixi.js as well?
https://npmjs.org/package/pixi.js
Side note, I am still maintaining my fork: https://npmjs.org/package/pixi
I saw in another thread this was brought up, should I rename the package to "node-pixi"? I wasn't thinking it would conflict with anything, I was just under the assumption that the "Pixi.JS" package that was on there would remain as such, and there's a long of packages named "node-something" on git, and just "something" on npm. That's where that comes from.
I did release pixi as well, but that is not what I meant when I posted that comment :)
I'm fine with you keeping your fork, and name it whatever you feel is appropriate. I went with pixi.js since pixi was taken on npm, but both our packages (npm/bower) are pixi.js now and that is fine.
Oh crap! I didn't even notice I was on a grapefruit repo, how did github search send me here?!
Sorry
Hehe no problem!