compress-json
pastml
compress-json | pastml | |
---|---|---|
4 | 1 | |
92 | - | |
- | - | |
8.4 | - | |
19 days ago | - | |
TypeScript | ||
BSD 2-clause "Simplified" License | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
compress-json
- Angular side compression and de-compression
-
Angular side string compression and de-compression
May be try this https://github.com/beenotung/compress-json
-
How to store your app's entire state in the url
Depending on how repeative the object keys are, you maybe able to save quite some spaces with compress-json [1].
Since the OP is using lz-string to do compression, I suppose the data should be repetitive.
[1] https://www.npmjs.com/package/compress-json
- Show HN: Reduce SQLite database size by up to 80% with transparent compression
pastml
-
How to store your app's entire state in the url
I imagine I'm not the first one to think of this, but a little while back I wrote a toy pastebin-like webpage that stored the code being rendered directly in the URL (with base64 and gzip compression to make it a bit smaller, although it still was quite large by usual standards). My thinking was that rather than having a centralized app for this publicly available, making a small page that could be statically hosted would make it easy for people or organizations to host their own page with whatever security they need (e.g. behind a firewall or VPN) and then the links could be shared privately on Slack or whatever without a need to add functionality for determining who should have access or how long to keep the code snippet around and instead just piggyback off of the privacy of whatever channel/DM they sent it across and how long the Slack instance is configured to retain history.
When I first came up with this idea, I was going to write some sort of server backend rather than just doing everything in the frontend, but once I started actually working on it, I realized that it wouldn't really add any value and it would make it a bit more annoying for people to self-host. Since then, I've wondered a bit how viable "static pages with state in the URL that can be easily self-hosted" would be as an alternative to a desktop GUI or Electron app for more technical users. One of the nicest parts of this approach to me is that I was able to make in only a few hours one evening despite knowing only the basics of webdev from maybe 8-10 years ago and next to nothing about programming GUIs in general. This makes me think that it wouldn't be too hard for people to fork and modify it to their own liking (e.g. changing the hard-coded style settings for rendering the code snippets), so there could be potential for an ecosystem to grow organically around something like this.
In case anyone is curious to take a look: https://gitlab.com/saghm/pastml/
What are some alternatives?
sqlite-zstd - Transparent dictionary-based row-level compression for SQLite
CozeJS - Coze Javascript - cryptographic JSON messaging specification
u - μ is a JavaScript library for encoding/decoding state (JavaScript object) in URL
sveltekit-search-params - The easiest way to read and WRITE from query parameters in sveltekit.
t
URLFormJS - URLFormJS - Create sticky forms, stateful applications, and shareable links.