v0.6.0
0.6.0 (2026-08-06)
Features
⚠️ Behaviour change — the REST API moved
NestLensConfig.path was documented as the base URL for the dashboard and its API, but nothing read it when mounting routes. It now works, which means the API sits under the configured prefix instead of the server root:
| before | after (default path) |
|
|---|---|---|
| Dashboard | /nestlens |
/nestlens — unchanged |
| REST API | /__nestlens__/api/* |
/nestlens/__nestlens__/api/* |
| SSE stream | /__nestlens__/stream |
/nestlens/__nestlens__/stream |
Nothing to do if you only use the dashboard — it is served at the same place and its own requests were updated.
Update your URLs if you call the internal API directly, for example scripted pruning:
- curl -X POST http://localhost:3000/__nestlens__/api/prune
+ curl -X POST http://localhost:3000/nestlens/__nestlens__/api/pruneWith a custom path, everything moves together:
NestLensModule.forRoot({ path: '/admin/monitoring' });
// dashboard → /admin/monitoring
// API → /admin/monitoring/__nestlens__/api/*This is the layout the FAQ and pruning docs already described — the code was the part that disagreed.
Shipped as a minor rather than a major because the package is still pre-1.0, where SemVer §4 allows breaking changes without a major bump.