Alternatives
Products that do what Fetch API compatible, complex form data / JSON body parser and guard does
Hi, We've been working on open sourcing our streaming complex body parser/guard and wouldn't mind some more people contributing. It features: - JSON, urlencoded AND multipart form data parsing - Out-of-the-box constraints for resulting object depth, key amount and size; definable globally and per call, preventing resource exhaustion by bailing on the stream if limits are exceeded - Multi-boundary (!) multipart form data parsing - Multidimensional array form data with auto-increment and explicit indexes (formElement[] vs formElement[0]) - Object form data with dot notation, including…
- 1

- 2LF
2017 · link.fish
- 3

- 4JM
2012 · github.com
- 5SF
2016 · github.com
- 6SA
2015 · github.com
- 7CL
2018 · github.com
- 8IB
Hey HN, A CSV parser using Go 1.26's experimental simd/archsimd package. I wanted to see what the new SIMD API looks like in practice. CSV parsing is mostly "find these bytes in a buffer"—load 64 bytes, compare, get a bitmask of positions. The interesting part was handling chunk boundaries correctly (quotes and line endings can split across chunks). - Drop-in replacement for encoding/csv - ~20% faster for unquoted data on AVX-512 - Quoted data is slower (still optimizing) - Scalar fallback for non-AVX-512 Requires GOEXPERIMENT=simd.…
Jan 2026 · github.com
- 9TF
Jul 2026 · github.com
- 10SS
Hi HN, I’m building SEE (Semantic Entropy Encoding): a searchable compression format for JSON/NDJSON. Goal: reduce the “data tax” (storage/egress) and “CPU tax” (decompress/parse) by keeping JSON searchable while compressed, with page-level random access. I just published a proof-first evaluation release: Offline DEMO ZIP (~10 min): prints compression ratios + skip rates + lookup latency (p50/p95/p99) DD pack: audit/repro evidence (decode mismatch=0, extended mismatch=0, audit PASS) Latest release:…
Feb 2026 · gitlab.com
- 11PC
2016 · github.com
- 12IH
A simple Go-based HTTP proxy designed for detailed inspection of requests and responses. It logs traffic to the console with colorization, automatic decompression, and formatting for common content types, while remaining transparent to the client application. Ideal for debugging API interactions, understanding middleware behavior, or simply getting a clear view of HTTP traffic flow with jq-like pretty-printing & colorization of request/response. Automatically redacts parts of Authorization header to avoid token leakage.
2025 · github.com
- 13JI
2018 · kantord.github.io
- 14MO
2020 · jsonformatter.live
- 15NJ
2017 · github.com
- 16JA
2015 · github.com
- 17AE
2015 · github.com
- 18JF
2017 · github.com
- 19L0
What's your tool chain for data and document processing? - jq is great, but limited to JSON; and jQuery limited to HTML; templating systems get messy for non-trivial logic; TypeScript lacks pattern matching and schema support. So I built Lambda — an expressive functional language that combines the power of Lisp, TypeScript, and many DSLs like jq, jQuery, RelaxNG, etc. It has a lightweight 9 MB runtime, built from scratch in C/C++, that provides an end-to-end document processing pipeline (parse → validate/query/transform → layout → render/view). Internally, Lambda parse…
Mar 2026 · github.com
- 20JP
A JSON parser in c with some SIMD optimisation for skipping whitespace. The numerical and string parsing functions split out so they are independantly runnable. They were for me the 2 most difficult to understand how they work and to show how the parser was composed of lots of smaller parsers.
2023 · github.com
- 21IL
2017 · github.com
- 22JS
Relatively simple currently, but figured I'd post for some feedback. I started this project last year but somewhat abandoned it. This feels like something which most likely already exists, but I couldn't find anything at the time I made it. I feel like my write up on the repo is pretty good at explaining the inspiration and purpose of this package; "Let's say you have an API, and you're looking for a method by which you can increase performance of your app via doing transformations of the data directly in the API. In this scenario, you would middleman the API returned data through a Fluxduct…
2022 · github.com
- 23XS
Hi HN. I made a little JS library for streaming structured data from LLMs using leniently-parsed XML as a medium. E.g. await simple('fun pet names', { schema: { name: Array(String) }, model: 'openrouter:mistralai/ministral-3b' }); // => ["Daisy", "Whiskers", "Rocky"] Demos: xmllm.j11y.io When using LLMs, I've ended up gravitating towards boring time-tested XML-esque tag-based delimiters instead of JSON/function-calling for the following reasons: - Diverse presence in training corpuses (consider flavours of content commonly adjacent to these syntaxes vs. JSON) - HTML was…
2024 · github.com
- 24SJ
2016 · s.codepen.io
Ranked by how close each launch is in meaning, then by votes. Refine with a description →