Release 1.5.1 (released November 10, 2026)
Bug Fixes & Improvements
- Installing
pp-devno longer pulls in theglobandminimatchversions thatnpm auditreported as moderate vulnerabilities; they only came in throughsvgtofont, which is now an optional dependency. svgtofontis no longer installed withpp-devby default. If you usepp-dev generate-icon-font, add it to the project withnpm install --save-dev svgtofont; without it, the command now exits with a message telling you what to install.
Release 1.5.0 (released November 9, 2026)
New Features
- You can now work in the Dev Panel as other MI users. Each saved user gets its own host (
<name>.localhost:<port>), and pp-dev proxies that host's requests to MI as that user, with its own cookies and cache. - The Dev Panel has a new Users section for adding a user by API token or by username and password, and for editing, opening, logging in to, removing, or setting the default user for
localhost. - New
users.persistoption keeps users added by API token between dev server runs, stored locally under~/.pp-dev/users/. - New
server.allowedHostsoption (Vite's syntax) lists the host names the dev server accepts, for use with tunnels. - Backups now keep only the 20 newest copies of a page by default. The new
sync.maxBackupsoption changes that number, andsync.buildTimeoutMslets a sync's build run longer than the default 10 minutes. - The Variables Editor renders variable descriptions as markdown, matching MI, and shows an Update local pages button in the Values tab when a local page's values differ from what was just saved.
- The Request Inspector now shows which saved user made each request, with a filter by user, and displays gzip, br, and deflate responses unpacked.
Bug Fixes & Improvements
- Hardened the internal API, the Request Inspector, and the
pp-dev nextdev-panel WebSocket against cross-site requests that could otherwise act with your MI token. pp-dev nextnow validates the request Host (and WebSocket upgrades) the same way Vite does, accepting only localhost, an allowed host, or an IP address.pp-dev nextnow restarts its server in a new process when a config file changes, so edits towithPPDev()ornext.config.*take effect instead of killing the dev server.- Fixed page content under
pp-dev nextbeing cut short or sent with a wrongContent-Length, and binary files under the base path being corrupted./favicon.icois now proxied to MI. - MI's own redirects, error pages, and maintenance pages now display correctly instead of looping through login, and large or binary MI responses are streamed without corruption.
- Template sync is more reliable: only one sync runs at a time, closing the sync dialog cancels the sync, and a sync's build now stops cleanly on timeout or when the dev server stops.
- The Variables Editor now surfaces every failed save, keeps edits made during a reload, and runs one save at a time so values are no longer lost or misflagged.
- Fixed several CLI and config issues, including
migrate --dry-runnot printing the migrated config andpp-dev optimizeloading the wrong environment mode.
Release 1.4.7 (released October 22, 2026)
- Raised the
vitedependency to^8.3.4to fix six security advisories (one high, four moderate, one low) in Vite 8.3.0–8.3.2, three of which came from its bundledlaunch-editor.
Release 1.4.6 (released October 15, 2026)
- Fixed the proxy cache not working when using a personal access token (
mi.tokenorMI_ACCESS_TOKEN); it was being cleared on almost every API response. With a token, the cache now clears only when the token itself changes; cookie-based sessions still clear it on login and logout as before.
Release 1.4.5 (released October 9, 2026)
- Updated dependencies to fix security advisories in
proxy-addr(critical),sharpandsource-map-js(high),ip-address(moderate), andserialize-javascript(low).
Release 1.4.4 (released October 5, 2026)
- Updated dependency versions, including
undici(used bycheerio),brace-expansion, andhttp-cache-semantics, to address newly reported high-severity security advisories.
Release 1.4.3 (released September 29, 2026)
- The regular login form now works in Safari on an HTTP dev server: proxied MI session cookies no longer carry
Secure,SameSite=NonebecomesLax, and theDomainattribute is removed. - Fixed the dev server crashing with
ERR_HTTP_HEADERS_SENTwhen page data couldn't load on/homeafter login, and a failed login no longer sends every later login attempt back to the login page. - Portal page assets no longer stay broken after logging out and back in: the proxy cache now stores only successful
GETresponses and never replaysSet-Cookie, and it clears whenever the MI session changes, including after a token login through/@api/login. - Fixed portal page images showing as black boxes in browsers such as Safari after a new login, by sending proxied MI responses with
Cache-Control: no-store. Repeat loads stay fast through the proxy cache.
Release 1.4.2 (released September 23, 2026)
- Removed stale dev route types before running
next build, underpp-dev next-build. - Replaced the
extract-zipdependency with validated JSZip-based extraction for improved security.
Release 1.4.1 (released September 4, 2026)
- Build output now normalizes SVGs to match how MI re-serializes them server-side.
- The Variables Editor now accepts numeric values for non-static select and multi-select list columns.
- Fixed the Variables Editor rendering
{id, text}options incorrectly in list-column select validation warnings. pp-dev migratenow reads the pp-dev config frompackage.json.
Release 1.4.0 (released August 28, 2026)
New Features
- The Variables Editor can now import variable values from another page.
Bug Fixes & Improvements
- Fixed the Variables Editor rendering
{id, text}options incorrectly in list-column select widgets. - The Variables Editor now allows manual input for non-static list columns and treats a null list value as an empty array.
Release 1.3.0 (released August 19, 2026)
New Features
- Redesigned the Variables Editor's Schema and Values tab UX.
Bug Fixes & Improvements
- The Variables Editor now guards against missing browser APIs instead of failing.
- The proxy now rejects unvalidated symlinks after zip extraction, closing a security gap.
- Fixed the proxy rewriting JSON and XML streamed responses and respecting client backpressure.
- Fixed the proxy rewriting URLs and forwarding the correct status for streamed responses.
Release 1.2.2 (released August 10, 2026)
Bug Fixes & Improvements
- Build output paths and sync backups are now resolved and preserved securely, including an explicit relative
backupFolderresolved against the project root, and packaging paths resolved against the Vite project root. - Fixed
MI_*environment values leaking across sequential project roots. - Prevented unsafe HTML rendering in the Variables Editor and secured its data integrity end to end.
- The popup close control is now an accessible button with a wider, 24px hit area.
- The Variables Editor now handles a failed fetch instead of hanging, and no longer shows a false-positive whitespace warning for variable names.
- Removed an invalid bundled npm patch.
Release 1.2.1 (released August 7, 2026)
Bug Fixes & Improvements
- Fixed a regression introduced in 1.2.0 where the Variables Editor's script could fail to parse, blanking out the entire Dev Panel UI.
Release 1.2.0 (released August 7, 2026)
New Features
- New Variables Editor for editing a Template's Variable schema and an App's live Variable values, with Schema and Values tabs, raw-JSON view for each, and JSON import/export for Values. Adds [Reload variables] and [Open variables editor…] buttons to the Dev Panel.
- Added an Auto/Dark/Light theme switcher to the Dev Panel's settings popover. The Inspector and Variables Editor, previously dark-only, now support it too.
- New App-variables API (
/@api/variables/*) with schema, export, and validation helpers.
Bug Fixes & Improvements
- Variables Editor tab switching no longer blanks out while a network request is pending, it shows cached content or a skeleton immediately and debounces the background reload.
- Added a delete-confirmation step for variables and a simpler way to reveal advanced fields in the Schema tab.
- Resolved new
npm auditfindings across the package and its test fixtures.
Release 1.1.1 (released July 27, 2026)
- Patched dependencies flagged by
npm auditto close known security advisories in pp-dev's dependency tree. No functional changes.
Release 1.1.0 (released July 21, 2026)
Next.js Build Parity
- Added a new
pp-dev next-buildcommand so Next.js Apps get the same build output thatpp-dev buildalready produces for other App types: aVERSIONfile, aBUILD-MANIFESTfile, and a zippeddistpackage. - pp-dev now shows a console warning when a Next.js App wrapped with
withPPDev()is built using plainnext buildinstead ofpp-dev next-build, so a manifest-less build doesn't slip through unnoticed. - Added CLI flags (and matching environment variables) to customize the
dist-zipfolder and filename, and to turn the version manifest on or off, for bothbuildandnext-build.
Bug Fixes & Improvements
- Fixed a logging issue where pp-dev reported writing the
VERSIONandBUILD-MANIFESTfiles even when the version file was disabled. - Resolved new
npm auditadvisories surfaced in pp-dev's dependencies and test fixtures.
Release 1.0.0 (released July 13, 2026)
pp-dev 1.0.0 is the first stable release. It adopts semantic versioning, requires Node.js 24 or later, and introduces a new configuration format.
Configuration Format Changes:
- Flat 0.x options are replaced by a grouped config. Run
npx @metricinsights/pp-dev migrateto convert an existing config automatically, it backs up the original before overwriting. - Legacy
pp-watch.config.*files are no longer read directly, the migrate command still detects and converts them.
New Features
- Added a Request Inspector to the Dev Panel for inspecting requests proxied through pp-dev during local App development. It exposes its own REST API for tooling and AI agents.
- Dev Panel position is now configurable, and the panel can be hidden automatically or manually.
Bug Fixes & Improvements
- Fixed the Request Inspector not capturing the bodies of proxied
PUTandPOSTrequests. - Refined the Dev Panel UI to align with core Metric Insights design.