You could install the optimizer Inkscape uses internally and process your files with a super simple shell script. When reading the inkscape command line help, it does not seem to offer any option to export optimized SVGs from there. Source: about 3 years ago

Inkscape uses Scour under the hood for optimized SVG export. Source: over 3 years ago

First make sure all your icons are saved as 'Optimized SVG' to remove Inkscape specific data and unnecessary id-attributes. Inkscape uses 'Scour' for this under the hood, so you can just use that directly to convert your files from the command line. I recommend the options --strip-xml-prolog --remove-metadata --enable-id-stripping --renderer-workaround. Now you only need to replace the outermost ... With ... For... Source: about 4 years ago

The script optimised the SVG using Scour. This removes some metadata and also shortens IDs as well as strip out comments. For the PNG files we used OptiPNG on the maximum optimisation setting. This can be slow on larger files, but for favicons should not take long. Here’s the before and after comparison of files sizes for a particular favicon, using the script:. - Source: dev.to / about 4 years ago

I also recommend Inkscape, it also has scour built-in to it. When saving a SVG select the option "optimized SVG" which will give you options to pass to scour to lower the amount of markup there is. You can then do some hand editing after this to further remove any markup you don't want. Source: over 4 years ago

I think a neat route would be to use this as an authoring plugin in VS Code, like prettier: write Duper (or JSON5, or whatever), and then downlevel it to regular json automatically when pressing cmd-s. You wouldn't get to keep your comments (or they could be transformed to { "//": "comment text" }). Outside of that, it's tough to compete with JSON in the "human readable unschematized serialization format" market,... - Source: Hacker News / 9 months ago

React's bundling system and published packages has gotten noticeably more complicated over time. First, there's the separation between the generic cross-platform `react` package, and the platform-specific reconcilers like `react-dom` and `react-native. All the actual "React" logic is built into the reconciler packages (ie, each contains a complete copy of the actual `react-reconciler` package + all the... - Source: Hacker News / 9 months ago

These numbers don't reflect anything useful. This is the total size of the code in the package, most of which will be tree-shaken. In Zod's case, the package now contains three independent sub-libraries. I recommend plugging a script into bundlejs.com[0] to see bundle size numbers for a particular script [0] https://bundlejs.com. - Source: Hacker News / about 1 year ago

[bundlejs](https://bundlejs.com/) is the better alternative to check your dependency sizes with. - Source: Hacker News / over 1 year ago

I was closing out some long lived issues over on bundlejs, when issue #50 reminded me of the ongoing debate about how bundlejs should handle the ESM and CJS packages. - Source: dev.to / about 3 years ago