It would be incredibly useful if caman.js could make use of https://www.npmjs.com/package/node-pre-gyp to ensure that there is a compiled binary available, so that people don't need to actually build caman.js themselves on install/update. Especially in Windows machines, the compilation turns npm install caman --save into "let's not install this, it doesn't work" (in theory it might turn into "let me learn how to set up a C++ build environment", but that takes so long that it's far more effective to say "screw this" and find something else =) and that's rather a shame, especially if they just want it for browser deployment, for which compilation isn't even necessary at all.
(for instance, in order to create a deploy bundle using browserify or webpack, the fact that the browser version is available for bower is, essentially, irrelevant, because bundling is based on node module require calls, even if those are require("caman/dist/caman.min.js"))
It would be incredibly useful if caman.js could make use of https://www.npmjs.com/package/node-pre-gyp to ensure that there is a compiled binary available, so that people don't need to actually build caman.js themselves on install/update. Especially in Windows machines, the compilation turns
npm install caman --save
into "let's not install this, it doesn't work" (in theory it might turn into "let me learn how to set up a C++ build environment", but that takes so long that it's far more effective to say "screw this" and find something else =) and that's rather a shame, especially if they just want it for browser deployment, for which compilation isn't even necessary at all.(for instance, in order to create a deploy bundle using browserify or webpack, the fact that the browser version is available for bower is, essentially, irrelevant, because bundling is based on node module
require
calls, even if those arerequire("caman/dist/caman.min.js")
)