Urgent.News

What's breaking now, across thousands of outlets.

Tech

I built 59 free browser-based dev tools in vanilla JS — here's what I learned

I've been quietly building Antigravity Tools — a collection of 59 free, browser-based developer utilities — and today I'm sharing everything I built and learned. Why vanilla JS? No React, no build step. The main constraint I set for myself: zero dependencies, zero server, zero telemetry . When you paste your JWT token into jwt.io, it goes to their server. When you use an online regex tester, your…

In the span of a few months, I developed a suite of 59 free, browser-based developer tools called Antigravity Tools. These tools operate without any dependencies, without any server, and without any data being sent to external servers. All operations occur within your browser using native APIs such as Web Crypto API, Canvas API, Web Audio API, and IndexedDB.

The 59 tools are divided into eight categories. Security and authentication tools include a JWT Inspector for decoding and checking JWTs, an RSA and ECC Key Generator for creating 2048-bit key pairs, and a PII Masker for removing sensitive information from text. AI and prompting tools consist of an AI Token Counter for estimating costs across various language models, a System Prompt Builder for creating agent instructions, an AI Text Humanizer to make AI output sound more natural, and a Prompt Cost Trimmer to reduce API costs by compressing prompts.

Development and code tools in the suite include a JSON Workbench for beautifying, validating, and converting data to various formats, a cURL Converter to translate cURL commands into browser-based fetch, request, or API calls, and a Regex Tester for real-time matching and display of capture groups. The Cron Builder provides a visual editor for creating and understanding cron expressions, while a Git Command Helper helps build visual representations of complex Git commands like undo, squash, and cherry-pick.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

This story

This is one outlet's version. Read the fullest account.

Read the original at dev.to →

More in Tech

Page count is the wrong unit for estimating a PDF-to-text job

"How many pages?" is the first question anyone asks about turning a pile of PDFs into text, and it's the number that ends up in the estimate.

  • Page count is poor predictor of edits needed in PDF-to-text conversion
  • Spot types include fixes, manual review, and rerun through OCR
  • Script fixes 85% of issues, human needed for remaining spots

I treated publishing as a queue. The queue lied.

On September 11, the publishing ledger said 29 articles while the public profile showed 30 . I had one stale editor buffer, one repaired series assignment, and no trustworthy answer to a simple…

  • Reporter treated publishing system as a queue, but it was a small distributed system.
  • Multiple histories existed in the queue: editorial rotation, public list, and browser session.
  • Mistake assumed counts represented the same thing, leading to duplicate publications.

Getting the text out of five screenshots inside one PDF

The document is a three-page weekly ops report with five screenshots pasted in: a growth dashboard, a chat channel, a spreadsheet, an alert and a kanban board.

  • Five screenshots in three-page report contain diverse tools
  • ImgIn's OCR tool extracts text from all screenshots accurately
  • Spreadsheet data tab-separated for easy spreadsheet import

More from Saturday 12 September →