Skip to content

Releases: openapi-ts/openapi-typescript

v5.3.0

02 May 19:12
Compare
Choose a tag to compare

New features

  • New --make-paths-enum CLI flag by @berzi (#883)
  • New --path-params-as-types CLI flag by @Powell-v2 (#891)
  • Supports /** @constant */ JSDoc comments by @PhilipTrauner (#896)
  • You can now add your own custom comment header at the top of every generated doc (#904)

🐛 Bugfixes

  • Fixes inconsistent comment title (#904)

v5.2.0

13 Feb 06:31
Compare
Choose a tag to compare

New features

🐛 Bugfixes

  • Fixes CommonJS error for undici on older versions of Node

🐣 Minor changes

  • Tiny optimizations for a little speed boost
  • Updated schemas & examples

v5.1.1

24 Jan 02:47
Compare
Choose a tag to compare

⚠️ Changes

  • Removes CJS version from npm (to use CJS, use openapi-typescript@4). Version 5 switched to ESM as default anyway, and since tests are now testing ESM, the reliability of CJS was dubious (and there were TypeScript problems as well)

🐛 Bugfixes

v5.1.0

11 Jan 01:34
Compare
Choose a tag to compare

New Features

🐛 Bugfixes

v5.0.1

11 Jan 01:20
Compare
Choose a tag to compare

🐛 Bugfixes

  • Adds missing types for CJS build (#861)

v5.0.0

27 Dec 02:53
Compare
Choose a tag to compare

🦍 Major changes

  • Updates this library to full ESM! ✨ This is the future of JavaScript, and is now natively supported in Node 14+.

🐥 Minor changes

  • Now supports a URL() as input to make ESM usage easier (see example)

⚠️ Breaking changes

  • 5.x drops support for Node 12. If you’re still on Node 12, be sure to lock your version to 4.x.

v4.5.0

27 Dec 00:40
Compare
Choose a tag to compare

New features

v4.4.0

14 Oct 15:23
Compare
Choose a tag to compare

New Features

  • Adds TypeScript @deprecated comment to deprecated schema objects by @bunkscene

v4.3.0

30 Sep 22:29
Compare
Choose a tag to compare

🐣 Minor changes

  • In many areas, changed out any with unknown (#769). See #554 for more explanation / context

🐛 Bugfixes

  • An old bug is now gone! openapi-typescript would incorrectly generate { [key: string]: unknown } for a type when it may have been a string or number. Now it will generate a more generic unknown type, unless it knows it’s dealing with an object for sure.

v4.2.0

30 Sep 21:38
Compare
Choose a tag to compare

New Features

  • Reference arbitrary data on generated types via the properties key by @Peteck (#626)