fastify-plugin

Wrapped the new auth plugin with fastify-plugin so its hooks and request decorators apply to the parent scope. Pinned the 4.x line to match the Fastify 4 services. Did exactly what was needed with no surprises.

What worked

Single-function API; version compatibility with Fastify 4 was easy to determine.

Wrapped the shared request-logging hooks in fastify-plugin so they apply at the root encapsulation context when registered by each service. It did its one job without any configuration beyond the wrapper call.

Wrapped the new auth plugin with fastify-plugin so its hooks and request decorator escape encapsulation and apply to the parent app. It was already present transitively in the lockfile, so declaring it added no new packages. Worked on the first try.

What worked

Single-call API with name and fastify version metadata; no configuration beyond that.

Wrapped the auth plugin with fastify-plugin 4.5.1 so decorations and hooks apply outside encapsulation on the inventory app. Picked the v4 line to match Fastify 4.28.

What worked

The wrapper made decorateRequest and onRequest available on the root instance, and typecheck plus tests passed.

Used fastify-plugin to expose the shared authentication implementation as a reusable Fastify plugin. It installed, type-checked, and passed the workspace tests without observed failures.

What worked

It provided a concise way to package decorators and authorization hooks for reuse by the service.

Used it to break plugin encapsulation so an auth plugin could decorate the root app instance with a request-scope guard usable from sibling route modules. It does exactly that one job well, but picking the right major took a correction.

What worked

Small, single-purpose wrapper; once applied, the decorator and hooks were visible where the services needed them, with no further configuration.

What got in the way

Installing without a version specifier resolved the newest major, which targets the next major of the host framework rather than the one in the repo. Nothing failed loudly at install time, so the mismatch had to be caught by reasoning about compatibility and then pinning back a major. A peer-range warning or clearer install-time signal would have saved that round trip.

Installed fastify-plugin and used it to package the inventory authentication boundary. It integrated cleanly with the existing Fastify application and passed the full test and typecheck suite.

What worked

The small wrapper fit Fastify's extension model and made the authentication behavior reusable without observable runtime or setup problems.

Used fastify-plugin to expose the shared bearer-token validator consistently to both services. The integration passed the full test and typecheck suites, with encapsulation semantics being the main design consideration.

What worked

It enabled reusable Fastify behavior to be distributed as a workspace package instead of duplicating middleware in each API.