Closed RobLoach closed 5 years ago
Why? I mean, node-raylib
feels ok to me... and I understand the binding requires Node.js, right?
Been thinking you may have been right about questioning node-raylib
as a name for two reasons....
While it is Node.js for the desktop, it's technically not Node.js on the web through emscripten. Both cases, however, use JavaScript. So raylib-js
might make sense for both, and it would match the conventions of the other names.....
Still trying to figure out how it can be built for both cases though. Tried in three build systems.....
Again, the name change all depends on if the bindings for both desktop and web work. Then, raylib-js
makes sense... Until then, node-raylib
will do. :+1:
Would like to rename the name in the package.json to raylib
so that it becomes...
const r = require('raylib')
raylib-js
Will match the other raylib naming conventions :smile: