Skip to content

feat: add NestJS binding - #1

Open
KanerA wants to merge 2 commits into
mainfrom
claude/nestjs-cache-viewer-a1061d
Open

KanerA wants to merge 2 commits into
mainfrom
claude/nestjs-cache-viewer-a1061d

Conversation

@KanerA

@KanerA KanerA commented Aug 13, 2026

Copy link
Copy Markdown
Owner

Adds CacheViewerModule.forRoot(path, options), a dynamic module wrapping the existing Express middleware via configure()/MiddlewareConsumer, so the viewer mounts through Nest's module graph instead of main.ts. Requires @nestjs/platform-express (Nest's default) since it wraps the Express binding rather than reimplementing routing.

KanerA and others added 2 commits August 13, 2026 13:46
Adds CacheViewerModule.forRoot(path, options), a dynamic module wrapping
the existing Express middleware via configure()/MiddlewareConsumer, so
the viewer mounts through Nest's module graph instead of main.ts.
Requires @nestjs/platform-express (Nest's default) since it wraps the
Express binding rather than reimplementing routing.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
The lockfile committed with the NestJS binding was generated with npm 11
on Windows. It resolved file-type's optional wasm32 fallback chain
(file-type -> @napi-rs/wasm-runtime -> @emnapi/core, @emnapi/runtime)
without recording those two packages, which npm ci on CI's npm 10/Linux
rejected as an out-of-sync lockfile. Regenerating inside a node:20 (Linux)
container - matching the CI matrix - avoids that path entirely, since
platform-specific optional resolution differs by npm version/OS.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant