Make the library npm-compatible

[juliendargelos]

The npm package is accessible from https://www.npmjs.com/package/lightgl.js, I would transfer ownership if needed (and edit repository url in package.json).

Note that it implies pushing the built lightgl.js file.

[z3dev]

Forget it...

[njourdane]

Hello, I'm also very interested on this.

Publishing an npm package may really facilitate installation workflow for projects using npm.

[njourdane]

If you are worried about publishing the lightgl.js file, I don't think it's necessary, since we can build it with a npm script entry in package.json, ie:

"scripts": {
  "postinstall": "python build.py"
}

[z3dev]

It’s not a technical problem. This library is not maintained.

[njourdane]

My bad. Should you recommend an other light alternative to three.js for a new project?

[z3dev]

Sorry. I don’t have any recommendations. There are several alternatives, even using WebGL is possible.

[njourdane]

I found a pretty good list of alternatives, if someone is interested.

Maybe you can archive the project and add a warning on the readme saying this library is not maintained, with a link to this list?

[z3dev]

@evanw needs to decide. But I would say that this library needs to be put on ... HOLD

Of course, if someone else wants to support this library...