Peek v0.3.0

Peek v0.3.0 — local proxy and safe sharing.

Public previews now route through a loopback proxy that rechecks ownership of the verified dev port, with password protection, WebSocket origin validation, failed-auth throttling, private mode, and optional expiry.

Install: npm install -g @usepeek/peek@0.3.0

0.3.0 — 2026-10-10

• Route public tunnel traffic through a loopback proxy that rechecks ownership
  of the selected dev port before forwarding HTTP and WebSocket requests.
• Preserve HTTP framing and reject unsupported WebSocket upgrades with a
  complete response instead of a half-written handshake.
• Add --password with hidden terminal input and HTTP Basic authentication at
  the proxy. Peek removes the credential before requests reach the app.
• Throttle repeated failed authentication and validate the browser WebSocket
  Origin against the active preview URL.
• Add --private for previews without a public tunnel, explicit --public,
  and --expires for automatic teardown after first readiness.
• Show access mode and expiry in terminal output and JSON events.
• Explain why a preview is unreachable, including protected-preview and
  HMR/WebSocket diagnostics.
• Make shutdown deterministic and report the concrete reason when cleanup
  cannot confirm every descendant exited.
• Bound dev-server and tunnel output buffering, and stream the cached
  cloudflared download and checksum verification to lower peak memory on a
  first run.

Full live Cloudflare verification: docs/LIVE-VERIFICATION.md

Final @radityprtama/peek migration release

This is the final migration release for the former npm package, @radityprtama/peek. The supported package is now @usepeek/peek.

Version 0.2.2 keeps the existing peek command and update check for users of older legacy versions. When an interactive preview is ready, it displays a notice with the new install command. JSON output, CI, tests, and non-interactive use remain unchanged.

To migrate:

npm uninstall -g @radityprtama/peek
npm install -g @usepeek/peek
peek --version

The legacy package will receive no further feature releases. The canonical Peek v0.2.2 release contains peek doctor improvements and the ongoing package metadata.

Peek v0.2.2

Peek v0.2.2 moves the canonical npm package to @usepeek/peek. The CLI command remains peek.

What's new

• peek doctor now reports the Peek and Node.js versions, platform and architecture, project and package-manager detection, cloudflared availability, and actionable environment checks. Use peek doctor --verbose for more detail.
• Verified cached cloudflared binaries have their execute permission repaired when needed.
• Package metadata, install instructions, update checks, and release automation now use the @usepeek/peek scope.

Install or migrate

npm uninstall -g @radityprtama/peek
npm install -g @usepeek/peek
peek --version
peek doctor

Existing CLI commands and JSON output are unchanged. A final @radityprtama/peek@0.2.2 migration release is planned for the old package; it will show a migration notice only in interactive use.

The @usepeek/peek@0.2.2 npm package was published before this GitHub Release. The release workflow verifies that the published tarball matches the tagged source instead of republishing the same version.

Peek v0.2.1

What's New

Update notifications

Peek now checks for new versions in the background and lets you know when an update is available.

Update available 0.2.0 → 0.2.1
Run npm install -g @radityprtama/peek@latest

The update check is designed to stay out of your way:

• Runs in the background without blocking Peek startup
• Checks the latest version from the npm registry
• Caches results for 24 hours to avoid unnecessary requests
• Uses a short timeout and gracefully handles network or registry failures
• Never automatically installs updates
• Skips update checks in "--json", "peek doctor", CI, and test environments
• Supports "NO_UPDATE_NOTIFIER=1" to disable update checks
• Avoids duplicate registry requests when multiple Peek processes are running

Update notifications are shown only after your preview is ready, keeping the normal Peek startup experience clean.

Upgrade

npm install -g @radityprtama/peek@latest

Or run Peek directly with the latest version:

npx @radityprtama/peek@latest

Full Changelog: v0.2.0...v0.2.1

Peek v0.2.0

Peek v0.2.0 makes previews more reliable across common Node development servers and temporary network interruptions.

• Reconnects a dropped Quick Tunnel without restarting the dev server, and reports the new public URL.
• Adds --lan for same-network previews and --json for newline-delimited machine-readable events.
• Adds peek doctor for local checks and peek doctor --live for a temporary public preview check.
• Detects blocked tunnel hostnames, offers --host-header localhost as a remedy, and checks Vite HMR WebSocket upgrades when possible.
• Supports optional peek.config.ts with a tokenized command, port, provider, and QR preference.
• Strengthens port verification and descendant-process cleanup tests.

Peek remains usable with a plain peek command in projects with a dev script. Public Quick Tunnel URLs are temporary and do not add authentication.

v0.1.1

0.1.1 — 2026-09-24

• Release Peek under a new npm version after 0.1.0 was already published.
• Normalize the executable path in package metadata and verify the installed
  peek command in the package smoke test.

v0.1.0

0.1.0 — 2026-09-24

• Start a local dev script with pnpm, npm, Yarn, or Bun, or run an explicit
  executable with peek -- <command>.
• Detect and verify a reachable local server port before tunneling it.
• Download and verify a pinned Cloudflare cloudflared binary on first use.
• Create a temporary HTTPS Quick Tunnel and optionally display a terminal QR
  code.
• Stop the development server and tunnel together on exit or failure.

Full Changelog: v0.1.0...v0.1.0