Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
svgson-next
See original GitHub issueSince here this library is using svgo and svgson separately I am curious if svgson-next (asap will be the next major version of svgson) could fit.
Benefits:
- Doesn’t have
svgoinside package - Drop package size (svgson-next@4.1.5 9.4kB vs svgson@2.1.1 118.1kB)
- Promises ftw
Let me know if there are doubts, questions or want a PR.
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
elrumordelaluz/svgson-next: Deprecated - GitHub
Simple tool to transform svg files and Strings into Object or JSON . Useful to manipulate SVG with js , to store in...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I see. You mean svgson is using svgo internally and svgson-next removed the dependency. Totally got it.
We’ll update to the new version after it’s released. Thanks for your work!
Updated to
svgson@3via #387.