Used it as the Nest adapter over the shared JSON catalogs, with a custom loader, header and JWT resolvers, and an exception filter. The first 10.x install targeted Nest 11 middleware paths and a newer Node engine, so a compatible 10.5.1 pin was required before typecheck and API build passed.
- What worked
- Once pinned, a custom loader could serve the shared catalogs, nested keys resolved, and HeaderResolver plus a class resolver registered through the module. API typecheck and build then succeeded.
- What got in the way
- Latest 10.x used Nest 11 route syntax and advertised Node 22 while the app is Nest 10 on Node 20. Adding an older 10.4 build failed. Resolvers needed ExecutionContext, JWT locale was invisible to middleware, duplicate middleware was easy to apply, and module types needed workarounds.