Vercel Have Finally Killed Port Numbers (Portless)

The speaker introduces Portless as a new CLI tool from the Vercel Labs team, known for projects like Agent Browser and JSON Render. It primarily aims to replace traditional localhost port numbers with stable, named ones to prevent port conflicts during development. This is especially helpful when multiple AI agents or projects are running in different tabs and might otherwise encounter the "address is already in use" error. By ensuring a port is always available, it provides a more seamless experience for developers and automated processes. The video promises to explain how this works under the hood and whether it might interfere with your system.

The speaker demonstrates how to use the Portless proxy by running the "portless" command followed by a custom hostname and the application start command. By default, Portless exposes the app on a subdomain of .localhost using port 1355, which is a play on the word "less." Users can customize this behavior by starting the proxy on Port 80, which allows for clean URLs without port numbers, though this requires sudo permissions. The tool also supports HTTPS through a specific flag, which is useful for modern web development environments. Advanced options such as running the proxy in the foreground for debugging and escaping the proxy for standard command execution are also discussed.

This section dives into the technical details of how Portless operates through two distinct processes. First, when a Portless command is run, it checks if a proxy is active and finds a random free port between 4000 and 4999 to speed up the finding process. These details are stored in a root store JSON file, and the application is then started on that specific port using environment variables. Second, when a browser visits a Portless URL, the proxy performs DNS resolution and a TCP connection to look up the correct port in the JSON file. The proxy then forwards requests to the application and sends the response back to the browser, which even works for WebSockets.

The speaker addresses potential issues when using Portless with non-Next.js projects like Vite, which might reject unrecognized origins. To fix this, developers may need to set a specific host key in their configuration to disable origin checks and ensure the proxy can redirect traffic. While these solutions might seem extreme, they are manageable for local environments and likely to be refined in future updates. Vercel Labs intends to continue updating Portless, with planned improvements including native Windows support and better integration with other bundlers. The video concludes by encouraging viewers to explore other Vercel Labs projects like Agent Browser for better AI interaction with web browsers.