Investigate high severity vulnerabilities

[olayway]

Investigate and fix 11 high severity vulnerabilities reported by npm.

[PhilippeduPreez]

npm audit fix:

[PhilippeduPreez]

[PhilippeduPreez]

Also tried removing package.json.lock and node modules and run npm i --legacy-peer-deps.

[PhilippeduPreez]

It seems like d3-color not being 1.3.0 was causing the most problems, I tried following https://itnext.io/fixing-security-vulnerabilities-in-npm-dependencies-in-less-than-3-mins-a53af735261d to see whether it worked. It seemed like it worked with the project having 0 vulnerabilities. We will just have to check if forcing the update does not cause any problems as it is used in a couple of other packages

[olayway]

@PhilippeduPreez it seems that mermaid developers have already been working on it. The package which was causing the issue was dagre-d3, which they have just replaced with dagre-d3-es. I've seen they merged the changes only yesterday and for now only to the development branch, so we may need to wait until the next release. I'm marking this issue as blocked for now.

For reference:
mermaid-js/mermaid#3712
mermaid-js/mermaid#3666
mermaid-js/mermaid#3809

[sidharthv96]

@olayway I guess this should be fixed now?

[rufuspollock]

FIXED. We can close this as all resolved.

@sidharthv96 thanks for the prompt.