Developer Tools

chromium23.3k★

This is the open source browser engine that powers Google Chrome, Microsoft Edge, Brave, Opera, and most other browsers you use daily. If you're building a browser, an embedded web view, or anything that needs to render web pages, Chromium is the engine, on the GitHub mirror, BSD-3 licensed. To be clear: this is not a tool you install from npm. This is one of the largest open source projects in existence, millions of lines of C++. The GitHub repo is a mirror of Google's internal repository. Fully free and open source. Google funds most development. You can build Chromium from source and ship your own browser. The catch: unless you're building a browser or doing engine-level development, you don't interact with this repo directly. Most developers use Chromium through Electron, Puppeteer, or Playwright. Building from source takes hours on a powerful machine and requires specific toolchains. The star velocity reflects interest, not usability. This is infrastructure that 3 billion people use daily but almost no one builds from source.

react-pdf16.5k★

React-pdf lets you build them using JSX components. Instead of wrestling with a PDF library's API, you write `<Document><Page><View><Text>` just like you'd write a React component. The mental model is the same, the output is a PDF. Everything is free under MIT. No paid tier, no premium features. The library handles layout (flexbox-based), fonts, images, SVG, links, and page breaks. It works in Node.js (server-side generation) and in the browser. There's nothing to host for the library itself. `npm install @react-pdf/renderer` and start building. If you need server-side PDF generation at scale, you'll run a Node.js service, but that's your infrastructure choice. Solo developers: perfect for adding PDF export to a React app. Invoices, reports, anything you'd otherwise build with a Python PDF library. Small teams: great for any app that needs branded PDF output. The component model makes templates maintainable. Growing teams: it scales, but complex layouts with many pages can be slow to render. The catch: the flexbox layout engine is close to CSS flexbox but not identical. Some properties behave slightly differently, and you'll spend time debugging layout issues that "should work." Also, rendering speed. Complex multi-page documents can take seconds to generate. For high-volume PDF generation, you might want a dedicated service.

SponsorBlock13.0k★

SponsorBlock automatically skips sponsor segments, intros, outros, and other non-content sections in YouTube videos. It's a browser extension powered by a crowdsourced database: users mark sponsor segments, and everyone else's player skips them automatically. GPL v3. Covers more than just sponsors: intros, outros, "subscribe" reminders, non-music sections of music videos, filler, and previews. The community database has hundreds of millions of submitted segments. Works on YouTube in Chrome, Firefox, and Safari, plus third-party integrations in apps like NewPipe and Invidious. Fully free. No paid tier. Community-driven and donation-supported. Install the extension, watch a video, sponsor segments skip automatically. That's it. You can also submit segments yourself when they're missing. The catch: it depends on the community submitting segments. Popular videos get covered quickly. Obscure videos might not have segments marked yet. YouTube could also break the extension with player changes (it's happened before and been fixed quickly). And some creators argue this hurts their sponsorship revenue. Fair point, and you should decide where you stand on that. The tool works. Whether you should use it is a personal call.

winget-pkgs10.4k★

winget-pkgs is the community-maintained package repository behind Windows Package Manager (winget). It is to Windows what Homebrew's formulae repo is to macOS: the catalog of installable software. You run "winget install firefox" and this repo is where that manifest lives. Contributing a package means submitting a YAML manifest via pull request. Microsoft validates the installer (MSI, MSIX, EXE formats), runs automated checks, and merges it. The repo has thousands of packages and grows daily. If you maintain Windows software, getting your app into winget-pkgs is the easiest distribution channel Microsoft offers. For Windows developers, winget is now the default. It ships with Windows 11 and Windows 10 (recent builds). Chocolatey and Scoop still have larger catalogs and more flexibility for power users, but winget has the advantage of being built into the OS. Most teams will end up using winget for standard installs and Chocolatey or Scoop for the long tail. The catch: this is a manifest repo, not a tool you run. The value is indirect. And winget still lags behind Homebrew and apt in package count and community tooling. If you are on macOS or Linux, this is irrelevant to you.

extism5.5k★

Extism is a WebAssembly (Wasm) plugin system. It creates a sandbox where third-party code runs safely, can't access your filesystem or network unless you explicitly allow it. It's essentially a bouncer for third-party code. You define what the plugin can do, compile it to Wasm, and Extism handles the execution boundary. Works from Go, Rust, Python, Node.js, Ruby, and more. BSD-3 licensed. Fully free and open source. The team behind it (Dylibso) offers consulting but the framework itself has no paid tier. The catch: WebAssembly plugins are powerful but the developer experience is still rough. Writing plugins means compiling to Wasm, which limits your language choices and debugging tools. The ecosystem is young. You won't find a marketplace of pre-built Extism plugins. This is for teams building platforms where extensibility is a core feature, not for adding a quick plugin system to a side project.

nix3.0k★

This gives you safe, idiomatic Rust wrappers instead of raw unsafe libc calls. That's the whole pitch. The nix crate covers POSIX APIs across Linux, macOS, FreeBSD, and more. You get typed enums instead of integer constants, Result types instead of checking errno, and zero-cost abstractions over things like mmap, ioctl, and ptrace. It's been around since 2015 and is a dependency in hundreds of Rust projects. Everything is free. MIT licensed, no paid tier, no cloud service. You add it to your Cargo.toml and go. Solo developers building anything systems-level in Rust should already have this in their toolkit. Teams don't need to coordinate around it. It's a library, not infrastructure. The catch: it's Unix-only. Windows developers need something else entirely. And the API surface is massive. Not everything is equally well-documented. You'll occasionally hit a function that sends you straight to the man pages.

renode2.4k★

Renode does exactly that. Picture a virtual hardware lab where you run your actual firmware binary against simulated chips. built by Antmicro (embedded systems consultancy). Supports ARM Cortex-M/A, RISC-V, Xtensa, and other architectures. You define your hardware in a configuration file: CPU, memory, UART, SPI, I2C, GPIOs, and Renode simulates it cycle-accurately enough to run real firmware. Fully free to use. The license is listed as 'Other': it's the MIT license for most components. Antmicro provides commercial support, custom platform models, and integration services for enterprise customers, but the tool itself is free. Solo embedded developers: run firmware tests without buying dev boards. Small teams: CI/CD integration: test firmware on simulated hardware in your pipeline. Medium to large: simulate multi-device networks and test inter-device communication without a hardware lab. The catch: simulation is never perfect. Timing-sensitive firmware may behave differently on real hardware. Not every peripheral is modeled; you may need to write custom peripheral models for uncommon chips. And the documentation, while improving, assumes you already know embedded development. If you're not writing firmware, this tool has no use case for you.

dev30001.1k★

Dev3000 is a CLI tool that captures your entire development session: server logs, browser console output, network requests, screenshots, and user interactions in one unified timeline. From Vercel Labs. Free, MIT-licensed. Install via npm or bun globally, run d3k in your project, and it hooks into your Node.js server and browser. AI agents (Claude Code, Cursor, Windsurf) can read the live timeline for context. No persistent server required. The cloud collaboration features use Vercel Sandbox if you need to share sessions. If you use AI coding assistants and spend time context-switching between terminal logs and browser DevTools, this is directly useful. The CLI is free with no limits. Solo developers working with agentic tools are the target audience here. The catch: Vercel Labs means experimental. Headless capture mode has rough edges. Deeper cloud features will likely require deeper Vercel platform integration over time.