portless v0.10.2 update

Portless, a tool from Vercel Labs that swaps raw localhost port numbers for named local web addresses, is preparing a v0.10.2 release with fixes for HTTP/2 and proxy startup bugs. (github.com) Portless sits in front of local apps like a traffic cop: it starts a proxy, assigns each app a free port, and serves it at addresses like ` The project’s README says Hypertext Transfer Protocol 2 and HTTPS are enabled by default, and the proxy auto-starts when a developer runs an app. (github.com) The repository shows Chris Tate as the latest committer, and the docs app was updated with a commit labeled “Prepare v0.10.2 release” on April 14, 2026. The public repository had about 6,900 stars on GitHub when it was crawled this week. (github.com, github.com) The timing lines up with bugs users reported in the past week around first-load failures and proxy behavior. One open issue, filed April 9, says a Vite 7 app behind portless can fail on the initial page load with `HTTP2_PROTOCOL_ERROR` until the browser does a hard reload. (github.com) Another open issue, filed April 11, points to portless’s own Hypertext Transfer Protocol 2 server settings as the likely fix path. The report says Vite already adjusted its server settings, but that change does not help when portless is the reverse proxy the browser actually connects to. (github.com) That matters in local development because modern web apps often run several services at once: a frontend, an application programming interface, docs, and background tools. Portless is built to map those services to stable subdomains like `api.myapp.localhost` instead of making developers remember changing port numbers like 3000, 4123, or 4567. (npmjs.com, github.com) The package is still pre-1.0, and its README warns that state formats may change between releases. The npm page currently shows version 0.7.1 published four days ago, which suggests the v0.10.2 work is visible in the repository before a matching npm publish appears there. (github.com, npmjs.com) Portless also targets teams using Git worktrees, where multiple branches live side by side on one machine. Its npm documentation says linked worktrees automatically get branch-based subdomains, so a branch like `fix-ui` can run at `fix-ui.myapp.localhost` without extra setup. (npmjs.com) The release work does not close every rough edge. Open issues from the last few days also describe Node.js server-side certificate errors and Windows-specific behavior, showing the project is still moving quickly as more developers test it across browsers, frameworks, and operating systems. (github.com, github.com) For developers who want local environments to look more like production, v0.10.2 appears aimed at the fragile part of that promise: making the proxy start cleanly and keeping the first page load from breaking. (github.com, github.com)