You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Yes. ZenStackMiddleware currently only supports Express.js, but I am using NestJS with Fastify due to its superior performance benefits. The existing @zenstackhq/server/express middleware cannot be directly integrated into a NestJS Fastify project. Attempts to adapt parameters or simulate Express behavior (e.g., modifying MiddlewareOptions) have failed, likely due to incompatible request/response object structures or middleware execution flows.
Describe the solution you'd like
I request support for ZenStackMiddleware in NestJS Fastify projects .
Describe alternatives you've considered
Manual adapter layer : I attempted to wrap the Express middleware for Fastify by adapting req/res objects and parameters, but this failed due to deeper incompatibilities. Manual solutions are error-prone and require ongoing maintenance.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Yes. ZenStackMiddleware currently only supports Express.js, but I am using NestJS with Fastify due to its superior performance benefits. The existing @zenstackhq/server/express middleware cannot be directly integrated into a NestJS Fastify project. Attempts to adapt parameters or simulate Express behavior (e.g., modifying MiddlewareOptions) have failed, likely due to incompatible request/response object structures or middleware execution flows.
Describe the solution you'd like
I request support for ZenStackMiddleware in NestJS Fastify projects .
Describe alternatives you've considered
Manual adapter layer : I attempted to wrap the Express middleware for Fastify by adapting req/res objects and parameters, but this failed due to deeper incompatibilities. Manual solutions are error-prone and require ongoing maintenance.
The text was updated successfully, but these errors were encountered: