The Modern Dev Server (BrowserSync Replacement)

BrowserSync is deprecated in WP Rig 3.1+. The replacement is the modern dev server: an opt-in, Vite-like development experience that proxies your local WordPress install with fast rebuilds and live reload — no BrowserSync middleware.

Configuring

The modern server reads the same dev config as everything else (in config/config.json or config.local.json):

{
  "dev": {
    "browserSync": {
      "live": true,
      "proxyURL": "wprig.test:8888",
      "https": false,
      "keyPath": "",
      "certPath": "",
      "devPort": 3000
    }
  }
}
  • proxyURL — your local WordPress URL (port optional).
  • https + keyPath/certPath — for HTTPS local sites (generate certs with npm run generateCert).
  • devPort — the local proxy port (default 3000).

Running

npm run dev:modern         # start the modern dev server
npm run dev:modern:debug   # verbose logging + stack traces

Then visit http://localhost:3000 (or HTTPS if configured). The classic npm run dev loop still works and remains the default all-in-one workflow — the modern server is an alternative, not a replacement requirement.

Debugging

  • npm run dev:modern:debug enables extra logging and full stack traces; WPRIG_DEBUG=1 toggles debug logs generally.
  • Verify dev.browserSync.proxyURL is correct in your config.
  • Check that ports are free: the proxy devPort (3000) and LiveReload (35729).
  • Exit code 1? Re-run in debug mode for the error log.
  • Node 20+ required; dependencies installed? npm i.

BrowserSync legacy docs

The old BrowserSync documentation (Using BrowserSync with WP Rig) remains for archival purposes only — new setups should use the modern server.

Theme Configuration (the dev settings), Performance & the Asset Pipeline (what loads at runtime), and WP Rig Tools (the toolbar that appears in this environment).