webpack-svgstore-plugin
webpack-svgstore-plugin copied to clipboard
mrsum
Simple svg-sprite creating with webpack
Version 4.17.2 of lodash has these vulnerabilities - [CVE-2019-10744](https://saas.whitesourcesoftware.com/Wss/WSS.html#!securityVulnerability;id=CVE-2019-10744;orgToken=80cb2709-ea67-49ba-b454-5a8a3ddde458) - [CVE-2020-8203](https://saas.whitesourcesoftware.com/Wss/WSS.html#!securityVulnerability;id=CVE-2020-8203;orgToken=80cb2709-ea67-49ba-b454-5a8a3ddde458) - [CVE-2019-1010266](https://saas.whitesourcesoftware.com/Wss/WSS.html#!securityVulnerability;id=CVE-2019-1010266;orgToken=80cb2709-ea67-49ba-b454-5a8a3ddde458) - [CVE-2020-28500](https://saas.whitesourcesoftware.com/Wss/WSS.html#!securityVulnerability;id=CVE-2020-28500;orgToken=80cb2709-ea67-49ba-b454-5a8a3ddde458) Update to v4.17.21 fixes all vulnerabilities.
Hey @mrsum, is it possible to update, at least, `svgo`? It's using `0.7.1` and the current version is `1.0.3`. Probably it would be good to update `webpack` as well but...
Our project uses webpack-svgstore-plugin extensively and it would be a nightmare to have to change the library because of this vulnerability.
Raising this PR to handle accessibility issues caused by the SVG sprites. In Windows on NVDA and JAWs, screen readers struggle when they get to the sprite (ie. straight away...
I have an icon with a path like that:  When it got parsed by the **parseFiles** fn, it becomes broken because of NaN's in its path:  The problem...
Hi, I'm having issues where many (all) svg icons have the same class names, but different styles on them. I'm using `{ prefixIds: true }` to enable that plugin. By...
Reference: https://www.npmjs.com/advisories/577
