v2.0.0

BREAKING CHANGES

ts-evaluator now requires Node v18.20.0 or newer.

Major Changes

• feat: add TypeScript v5.6 support 73ed586

Other Changes

• chore: improve test runner b2deb18
• style: run prettier e7aac22
• chore: move from pretty-quick to lint-staged to support Prettier v3 129ff0d

v1.2.0...v2.0.0

v1.2.0

• feat: add TypeScript v5.1 support. Add support for newer JSDOM versions 6f06ef0
• Merge pull request #14 from astahmer/chore/update-deps f7ade86
• feat: add Typescript v[4.9.5 ; 5.1.6] support b699f23

v1.1.0...v1.2.0

v1.1.0

• feat: add TypeScript v4.9 support 590293c

v1.0.7...v1.1.0

v1.0.7

• chore: add null-check 3b365dd
• chore: update lock file deb1e34

v1.0.6...v1.0.7

v1.0.6

• feat: change error handling to a continuation function approach 8f7cfdb
• test: add an additional test b67b873

v1.0.5...v1.0.6

v1.0.5

• fix: add null-check to avoid runtime exceptions under some circumstances on returned values d89671c

v1.0.4...v1.0.5

v1.0.4

• feat: add 'ModuleOverrides' option. e121d66

v1.0.3...v1.0.4

v1.0.3

• feat: make evaluating identifiers more robust 8436f68
• feat: make behavior when not passing in a typechecker far more robust 5f6634f

v1.0.2...v1.0.3

v1.0.2

• feat: make passing in a typechecker optional and document its operation 3966d4b
• chore: update lockfile 7e5078c

v1.0.1...v1.0.2

v1.0.1

New Features

ts-evaluator is now based on ESM and requires Node v14.19.0 (BREAKING CHANGE)

Now that TypeScript v4.7 is out, it has finally received great support for ES modules in a Node.js environment that aligns with how it has been implemented across Node.js and browsers.

Because of this, now is a good time to make ts-evaluator a type: "module" package. However, it still provides a CommonJS fallback. If your codebase is still based on CommonJS, you should be fine. Please know however, that ts-evaluator requires an environment running Node v14.19.0 or newer going forward.

TypeScript v4.7 support

ts-evaluator now supports TypeScript v4.7 and its new features.

New presets: NODE_CJS and NODE_ESM

Nowadays, Node.js files may either be based on CommonJS or ES Modules, and depending on which it is, the execution environment has some differences. For example, in a CommonJS based Node.js file, globals like require, __dirname, and __filename is available, whereas import.meta is available in an ES Module based Node.js file.

To reflect this, two new Lexical Environment presets have been added to ts-evaluator:

• NODE_CJS - An alias for NODE.
• NODE_ESM - Assumes an ESM-based Node.js environment. This means that built-in modules such as fs and path can be resolved, and Node-specific globals such as process is present, as well as ones that are only present in an ESM-based Node.js environment, such as import.meta.

Support for evaluating new.target and import.meta

ts-evaluator can now handle new.target syntax, as well as import.meta syntax inside ES Modules.

v1.0.0...v1.0.1