The Swiss Army Knife of Vector Graphics Scripting – Scriptographer ported to JavaScript and the browser, using HTML5 Canvas. Created by @lehni & @puckey
Hello,
I'm currently using paperjs in my project which uses webpack. I use to install packages using only NPM, because it has become a wide option even for clientside libraries.
I noticed that install paperjs through NPN installs paper-core.js, paper-full.js and thats ok, but i t installs also paper-node which is, correct me if I'm wrong, the paperjs server side library for nodejs.
The problem is that the nodejs library has to be built on top of two other libraries cairo and pango that are canvas realted. This force me to install these two libraries even if I'm interested only in the client side/browser version.
So my question is, is there a way to prevent the paper-node build using NPM?
If this isn't possible, why don't you provide two versions of paper on NPM? (i.e. paper and paper-node)
Hello, I'm currently using paperjs in my project which uses webpack. I use to install packages using only NPM, because it has become a wide option even for clientside libraries.
I noticed that install paperjs through NPN installs
paper-core.js
,paper-full.js
and thats ok, but i t installs alsopaper-node
which is, correct me if I'm wrong, the paperjs server side library for nodejs.The problem is that the nodejs library has to be built on top of two other libraries
cairo
andpango
that arecanvas
realted. This force me to install these two libraries even if I'm interested only in the client side/browser version.So my question is, is there a way to prevent the
paper-node
build using NPM? If this isn't possible, why don't you provide two versions of paper on NPM? (i.e.paper
andpaper-node
)Thanks, Simone