Sample
fastify 5.12.0: Isolate decorators, lifecycle hooks, and error handlers within Fastify 5.12.0 plugin encapsulation scopes without leaking into root or sibling contexts
Verified sample for npm fastify 5.12.0: Isolate decorators, lifecycle hooks, and error handlers within Fastify 5.12.0 plugin encapsulation scopes without…
sha256:d61470b36d28e504209b5c16f625f64d76446839c46e9e50457686e5822f9720
This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured.
How many distinct signing keys filed a passing contract receipt. One is the author alone; more than one means somebody else built it too. A key is self-generated with nothing registered behind it, so it counts keys, not people.
MIT-0
Execution evidence
The declared environment and the signed runs are kept apart, so you can see exactly what this sample ran and where.
- Evidence basis
- Signed contract pass
- Verification receipts
- 2
- Signing keys that built it
- 2
Declared environment
node linux x64 node node npm
Verification-run environments
| Environment | Contract | Stages | Run |
|---|---|---|---|
| node 22 · linux alpine/x64 · docker ed25519:d91480838ac982c9 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · node-typescript@1 |
2026-08-17 |
| node 22 · linux alpine/x64 · docker ed25519:2175b912ea1c23b1 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · node-typescript@1 |
2026-08-18 |
Case
HOW- Goal
- Isolate decorators, lifecycle hooks, and error handlers within Fastify 5.12.0 plugin encapsulation scopes without leaking into root or sibling contexts
- Packages
- Symbols
-
- fastify
- fastify.register
- fastify.decorate
- fastify.hasDecorator
- fastify.addHook
- fastify.setErrorHandler
- fastify.inject
- Environment
- node
- Created
- 2026-08-17T12:50:47Z
Contract
- assert Fastify 5.12.0 encapsulates decorators and scoped error handlers within registered plugin contexts so they do not leak to root or sibling plugin instances
- assert lifecycle hooks registered inside an encapsulated plugin execute only for routes within that plugin scope while root hooks execute for all routes
- assert errors thrown inside an encapsulated plugin are handled by the scoped error handler while root errors fall back to Fastify default 500 error response
- assert app.inject executes all scoped requests in process without opening a listening socket
Files
- NOTES.md
- csx.json
- package-lock.json
- package.json
- test/contract.mjs