v4.0.0

BREAKING CHANGES

• Node 16 and 17 support has been dropped.

Changes

• feat: add TypeScript v5.6 support 3135c4f
• chore: move from pretty-quick to lint-staged to support Prettier v3 43be779

v3.0.0...v4.0.0

v3.0.0

• feat: add TypeScript v5.1 support 21bf22b

v2.0.4...v3.0.0

v2.0.4

• chore: bump deps d50b3ac

v2.0.3...v2.0.4

v2.0.3

• chore: bump dependencies a34d2b4

v2.0.2...v2.0.3

v2.0.2

• fix: fix cloning type parameter declarations 0d3c1a1

v2.0.1...v2.0.2

v2.0.1

• feat: handle decorated members b9b9791

v2.0.0...v2.0.1

v2.0.0

• fix: add import assertion 1e5835d
• feat: implement support for TypeScript v4.9 988b10d
• chore: bump dependencies 8e6406b

v1.0.0...v2.0.0

v1.0.0

New Features

The ts-clone-node package is now based on ESM and requires Node v14.19.0 (BREAKING CHANGE)

Going forward, the ts-clone-node package is now a type: "module" NPM package. There are still API entrypoints for CommonJS using the package exports feature, as well as pointed to from the main field in the package.json, so it should continue to work just fine in a CommonJS environment.

From this new major version of ts-clone-node, you must be using Node.js v14.19.0 or newer.

TypeScript 4.7 support bba8536

ts-clonenodenow support TypeScript 4.7 and specifically the newImportTypeAssertionContainer` node.

v0.3.32...v1.0.0

v0.3.32

• chore: run tests on Node v14, 16, and 17 to align with ESLint plugins b7ac20d

v0.3.31...v0.3.32

v0.3.30

• chore: bump dependencies 369fe07
• fix: support Identifier nodes with only escapedText. #6 9e5378c

v0.3.29...v0.3.30