LabscoMCP early access ↗
REPO PACKAGECOMMUNITY

vercel-labs portless

vercel-labs · publisher10,047 GitHub starsApache-2.0 · Listed as freegithub.com/vercel-labs/portless

LABSCO SUMMARY

Summary

vercel-labs/portless ships exactly 2 skills, both for someone adopting portless in their own project rather than for contributing to portless itself.

portless replaces a dev server's port number with a stable, named .localhost URL: wrap the existing script (portless myapp next dev instead of next dev) and the app is reachable at https://myapp.localhost with HTTPS and HTTP/2 on by default, through a locally generated and trusted certificate authority. It auto-discovers monorepo workspaces, gives each git worktree its own subdomain automatically, and can serve a custom TLD or LAN-visible hostname instead.

The two skills split along that same line. The portless skill covers setting portless up and troubleshooting it -- naming, the portless.json and package.json config fields, monorepo apps overrides, TLD choice, and LAN mode. The oauth skill is narrower: it exists because Google, Apple, Microsoft, Facebook, and GitHub sign-in flows often reject a .localhost redirect URI outright or throw "redirect_uri_mismatch," and it walks through reconfiguring each provider's console to accept a portless URL instead of plain localhost:PORT.

READ MORE

Who this is not for.

If your dev server never involves an OAuth sign-in, the oauth skill has nothing to fix, and if bare localhost:3000 URLs have never bothered you, neither skill is solving a problem you have.

One caveat from the README itself.

portless says plainly that it is pre-1.0: the on-disk state-directory format can change between releases, which can force a portless trust re-run, and different contributors on the same project may end up running different portless versions if it is installed per-project rather than globally.