canvg | JavaScript SVG parser and renderer on Canvas | Animation library

Found the solution.

in webpack.mix.js I had to add

As discussed in the comments you should update your webpack configuration to handle loading svg files. inside the module.rules array you should add the following:

Per the documentation for Canvg.from, you need to pass it your drawing context, not the canvas itself. So change this line:

It looks like your path variable isn't declared globally, but instead is declared in makeGraph(). Because it's declared in the "scope" of makeGraph(), tick() doesn't have access to it -- and thus you get the error path is not defined. (In the JSFiddle, path is declared globally.) So, you could just declare them outside of the function to start (just stick var path; at the top of your JS file, and then set it to the correct value in the makeGraph function), although there might be a better solution I don't know that's specific to D3.

It looks like once you fix that, you'll probably also get circle is not defined and text is not defined because they too are declared in makeGraph but then you try to use them in tick() -- so you'll have to globally declare them as well, if I'm reading your code right.

The error is clear, you are calling the class canvg without the new keyword.

Also, you referred to the GitHub Documentation where there is clearly write how to use it:

As said in the comments, I finally realised the nginx configmap was not needed, as the docker image embedded an nginx on its own.

Removing the configmap instructions in deployment.yaml did the trick !

It seems dependency error means that particular Module is missing when it's running.

Run npm ls or yarn list will print to stdout all the versions of packages that are installed, as well as their dependencies, in a tree-structure. Then search for that particulate packages are listed or not. Run npm ls jspdf or yarn list jspdf then you can see its list of dependencies in tree-structure.

Please check your node version is updated or not ? If not then update first.

Quick & Dirty way: delete package.lock or yarn.lock file and delete .node_modules folders And Then run npm install or yarn to install again. Look at console while you installing and make sure there are no error in the installing process. If you saw error you better look that massages also.