v5.0.0

[novemberborn]

Despite the major version bump this is a relatively minor release. Node.js 12 is no longer supported. The type definitions are now distributed to be compatible with TypeScript 4.7 or newer.

It's available as a pre-release under the next tag for the next few weeks:

npm install --save-dev ava@next

Breaking Changes

• AVA now requires Node.js 14.19, 16.15 or 18. Require Node.js 14.19, 16.15 or 18 #3043
• Type definition distribution is no longer compatible with TypeScript versions before 4.7. Require TypeScript 4.7 #3041
• We're now exporting types rather than interfaces. Update dependencies #3096

Improvements

• Detect process.exit() called from tests by @gibson042 in Detect process.exit() called from tests #3080
• Improve test result accessibility by @gibson042 in Improve test result accessibility #3082
• Parse for line numbers with latest supported ECMA version by @novemberborn in Parse for line numbers with latest supported ECMA version #3063
• Work around os.cpus() returning an empty array on unsupported platforms by @catink123 in Work around os.cpus() returning an empty array on unsupported platforms #3095
• Count timeouts separately from the timed out tests by @novemberborn in Count timeouts separately from the timed out tests #3099

New Contributors

• @Prinzhorn made their first contribution in Update 06-configuration.md #3073
• @catink123 made their first contribution in Work around os.cpus() returning an empty array on unsupported platforms #3095

Full Changelog: v4.3.3...v5.0.0

---

This discussion was created from the release v5.0.0.

[novemberborn]

Please let me know how this is working for you, especially the type definition changes. If it's all good I'll promote to latest on npm.

[catink123]

Okay, here's my tsconfig:

{
  "compilerOptions": {
    "module": "ES2020",
    "moduleResolution": "node",
    "rootDir": "src",
    "outDir": "dist",
    "lib": ["es2017", "es2021", "dom"],
    "target": "es2015"
  }
}

It actually may be wrong, because I still don't fully understand how to configure the compiler properly.

[novemberborn]

I forgot to include the new definition files in the package, but also it didn't work with your combination of ES2020/node. Could you try again now?

I think there are five combinations to take care of:

• commonjs/node
• commonjs/node16
• node16/node16
• es2020/node
• es2020/node16

[catink123]

Been busy for a while, but I did what you suggested. I've changed module in my tsconfig to es2020 (in lower-case), added --experimental-specifier-resolution=node as a Node argument to AVA configuration and now everything works! I suppose you'll merge the ts-node-resolution-shims branch and it'll be added to the 5.0.0 release.

[novemberborn]

Does it also work with the original configuration?

Using node16 for module and moduleResolution would be the expected configuration for a Node.js project. No need to add any flags within AVA. But you may need to set "type": "module" in your package.jsonfor TypeScript to emit ESM files (and Node.js to treat.js` files as ESM).

[catink123]

It doesn't work with node16 as module with this error:

ReferenceError: exports is not defined in ES module scope                       
This file is being treated as an ES module because it has a '.js' file extensi
on and '/data/data/com.termux/files/home/testproj/package.json' con
tains "type": "module". To treat it as a CommonJS script, rename it to use the '.cjs' file extension.

and it doesn't work with the original configuration without the --experimental-specifier-resolution=node Node flag, but that's a known problem with TypeScript, so I use this workaround.

Also, I'm developing a library targeting web browsers, so compatibility with Node isn't neccesary (if that's why you were saying about node16 for module for a Node.js project).