express-zod-api - npm Package Versions

v20.15.2

• Fixed duplicated client types in unions:
  • When splitResponse option is disabled on Integration primitive response types could have been duplicated.

- type GetV1AvatarSendResponse = string | string;
+ type GetV1AvatarSendResponse = string;

v20.15.1

• Deprecating serializer property on Documentation and Integration constructor argument:
  • That property was introduced in v9.3.0 and utilized for comparing schemas in order to handle possible circular references within z.lazy();
  • The property is no longer in use and will be removed in version 21.

v20.15.0

• Feat: warn about potentially unserializable schema used for JSON operating endpoints:
  • This version will warn you if you're using a schema that might not work in request or response, in particular:
    • Generally unserializable objects: z.map(), z.set(), z.bigint();
    • JSON incompatible entities: z.never(), z.void(), z.promise(), z.symbol(), z.nan();
    • Non-revivable in request: z.date();
    • Incorrectly used in request: ez.dateOut();
    • Incorrectly used in response: ez.dateIn(), ez.upload(), ez.raw();
  • The feature suggested by @t1nky.

v20.14.3

• Fixed: missing export of testMiddleware:
  • The feature introduced in v20.4.0 but was not available;
  • The issue reported by @Tomtec331.

v20.14.2

• Documentation: promoting Express 5 as the recommended version for new projects;
• Minor refactoring: response variant constraints, inverted definition of AbstractLogger type;
• There is now an opportunity to support the project with sponsorship: https://github.com/sponsors/RobinTail

v20.14.1

• node-mocks-http version is ^1.16.1:
  • This deduplicates the @types/express dependency to the version installed in your project;
  • This fix is an addition to the support of Express 5 (v20.10.0) and its types (v20.14.0).

v20.14.0

• Enabling usage of recently released @types/express@^5.0.0:
  • This is an addition to the support of Express 5 introduced in v20.10.0.

v20.12.0

• Feat: Graceful Shutdown
  • You can enable and configure a special request monitoring that, if it receives a signal to terminate a process, will:
    • first put the server into a mode that rejects new requests,
    • attempt to complete started requests within the specified time,
    • and then forcefully stop the server and terminate the process;
  • This feature utilizes a modernized fork of http-terminator.

import { createConfig } from "express-zod-api";

createConfig({
  gracefulShutdown: {
    timeout: 1000,
    events: ["SIGINT", "SIGTERM"],
  },
});