npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@elliat/json-compress

v0.0.3

Published

A quick general purpose compression / minification algorithm for JSON structures

Downloads

2

Readme

json-compress

Losslessly JSON objects. This works by renaming any strings in the input to shorter keys, combining it with a mapping. This minification applies even when gzipping the whole thing. In a benchmark this showed a substantial (~75%) improvement for uncompressed objects and a (>50%) improvement when compressing afterwards with gzip:

➜  assets git:(master) ✗ ls -1shS
total 2,8M
2,2M schema.json
520K schema-minified.json
 60K schema.json.gz
 28K schema-minified.json.gz

When should you use this?

Use this library to minify and unminify JSON objects that are going to be sent over the network. Use this especially when you:

  • Are stuck with JSON: using a binary format will be better hands-down but makes it harder to inspect data
  • Have JSON objects with repeating keys and strings, like the schema format we use with Fonto (conveniently added as an example). Don't use this when your keys and values are not repeating. There's no use, it will just make the JSON hard to read...
  • You want to reduce the network overhead for your JSON endpoints with minimal impact on your existing APIs / served mimetypes

How do I use this?

See the tests! If you want to minify JSON served by your server just import doMinify from this package, call it with the raw data (as an JSON object) and serve the return.

On the client side, imoprt doUnminify from this package, call it with the minified data and work with the return value of this function!

Should I still use GZIP?

Yep. This is a last-crumbs optimization! GZIP over JSON strings compresses them well, but this adds the last bit!

You're removing repetitions, GZIP should remove repetitions as well, what's up here?

My thoughts exactly, but empirical evidence shows the results. Check them yourself of you want!

➜ cd /tmp
➜ git clone git+ssh://www.github.com:DrRataplan/json-minify
➜ cd json-minify
➜ npm i
➜ npm test
➜ cd assets
➜ gzip *.json -k
➜ ls -1shS
total 2,8M
2,2M schema.json
520K schema-minified.json
 60K schema.json.gz
 28K schema-minified.json.gz

Seeing different results, or did I make a mistake? Reach out!

Is this free?

As in free beer.