brotli-wasm
sveltekit-search-params
| brotli-wasm | sveltekit-search-params | |
|---|---|---|
| 2 | 3 | |
| 248 | 426 | |
| 3.6% | - | |
| 6.0 | 8.1 | |
| 28 days ago | about 2 months ago | |
| TypeScript | TypeScript | |
| Apache License 2.0 | MIT 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.
brotli-wasm
-
Compress a file using Brotli client side
The only solution I can see is to use a wasm polyfill like this, even though I know browsers support brotli. Is there a way to brotli compress a file without using polyfills?
- How to store your app's entire state in the url
sveltekit-search-params
-
How did you accomplish complex search and filter with query params?
I saw paoloricciuti/sveltekit-search-params posted somewhere, I haven't used it but it looks very good.
-
How to store your app's entire state in the url
This is quickly becoming a standard in apps and it really shouldnt be handrolled since its such a common requirement and easy to get wrong (between serializing/deserializing/unsetting states). In Svelte it is now as easy as using a store: https://github.com/paoloricciuti/sveltekit-search-params
in general i've been forming a thesis that there is a webapp hierarchy of state that goes something like:
1. component state (ephemeral, lasts component lifecycle)
2. temp app state (in-memory, lasts the session)
3. durable app state (persistent, whether localstorage or indexeddb or whatever)
4. sharable app state (url)
5. remote user data (private)
6. team user data (shared)
7. global data (public)
and CRUD for all these states should be as easy to step down/up as much as possible with minimal api changes as possible (probably a hard boundary between 4/5 for authz). this makes feature development go a lot faster as you lower the cost of figuring out the right level of abstraction for a feature
-
Is there anyway to change the URL in an endpoint?
I think this library is a potential use case for you https://github.com/paoloricciuti/sveltekit-search-params
What are some alternatives?
CozeJS - Coze Javascript - cryptographic JSON messaging specification
u - μ is a JavaScript library for encoding/decoding state (JavaScript object) in URL
t
URLFormJS - URLFormJS - Create sticky forms, stateful applications, and shareable links.
pastml
calculang - calculang is a language for calculations 🧮💬👩💻
urltron - Stringify and parse json as url query paramaters
houdini - The disappearing GraphQL client
lighthouse - Automated auditing, performance metrics, and best practices for the web.