GNext is a collection of developer utilities and technical references at gnext.dev. It exists because the everyday tasks of development (format this JSON, decode that token, check this cron line, work out a subnet) deserve tools that are fast, precise about what they do, and honest about where your data goes.
What is here
At launch: 17 tools, 4 references and 3 guides. The tools cover JSON, YAML and CSV; Base64 and URL encoding; JWTs and hashes; UUIDs and random strings; regular expressions; cron; timestamps; file permissions; and subnets. The references cover HTTP status codes and methods, Git commands and regex syntax, each written from the primary specification and dated when it was last checked.
How the tools work
Every tool runs as JavaScript in your browser. There is no backend: the site is static HTML, CSS and JavaScript served from a plain web server. When you paste text into a tool, it is processed on your device and never transmitted. Files opened with a tool are read with the browser’s File API, locally. Each tool page says this explicitly, and the privacy page describes the site-wide posture, including what the server does see.
The implementations are small and deliberately dependency-free where practical. The JSON tools use a hand-written parser so that error messages can name the line, the column and the likely cause. The hash tool uses the Web Crypto API. The YAML converter is the one exception: it uses the js-yaml library, loaded only on that page.
What GNext is not
It is not a blog, a directory of other people’s tools, or a landing page for a product to be announced later. There are no accounts, no plans, no usage counters and no testimonials. If something on the site is inaccurate, that is a bug, and the reviewed date on reference pages exists so you can judge how current they are.
Standards and sources
Reference material is written from the RFCs and specifications it describes: RFC 9110 and the IANA registry for HTTP, RFC 8259 for JSON, RFC 4648 for Base64, RFC 7519 for JWT, RFC 9562 for UUIDs, RFC 4180 for CSV, the official Git documentation, and ECMA-262 for regular expressions. Where a tool follows one dialect among several (cron, regex), the page says which.
Roadmap
The launch set was chosen for depth over breadth. Planned additions follow the same rule of one careful tool at a time: JSON diff and JSONPath, XML and HTML formatting, more encoders (HTML entities, hex, Unicode), semver and diff utilities, and individual HTTP status code pages where a code deserves more than a paragraph. The search palette (Ctrl K) already indexes everything on the site, so new tools become discoverable as soon as they exist.
Contact
Found an error or want to suggest a tool? Email [email protected].