AssertionError when debugging in VS Code

[Basssiiie]

Hey I've been using the VS Code debugger launch configuration from here for quite a while now, but since updating to V4 I cannot get it to work anymore. Whenever I run it, I run into this error on any of the test files:

  Uncaught exception in tests\temp.tests.ts

  AssertionError [ERR_ASSERTION]: The expression evaluated to a falsy value:

    assert(refs.runnerChain)


  × tests\temp.tests.ts exited with a non-zero exit code: 1
  ─

  1 uncaught exception

The example test file used (the error occurs on any test file though):

import test from "ava";

test("ava test", t =>
{
	t.pass();
});

The VS Code launch.json (exact copy from the linked docs):

{
	"version": "0.2.0",
	"configurations": [
		{
			"type": "node",
			"request": "launch",
			"name": "Debug AVA test file",
			"runtimeExecutable": "${workspaceFolder}/node_modules/.bin/ava",
			"runtimeArgs": [
				"${file}"
			],
			"outputCapture": "std",
			"skipFiles": [
				"<node_internals>/**/*.js"
			]
		}
	]
}

AVA configuration in package.json:

	"ava": {
		"extensions": [
			"ts"
		],
		"files": [
			"tests/**/*.tests.ts"
		],
		"require": [
			"./tests/_setup.js",
			"ts-node/register"
		],
		"verbose": true
	}

Running npx ava --version reports 0.1.0? I have 4.0.1 installed according to the package.json and the node_modules/ava folder and both npm install and npm update do not change that.

AVA debugging still works in another project running 3.15

This sounds like a bug right?

Thank you for your time!

[novemberborn]

That is peculiar. Are you breaking on (un)caught exceptions by any chance? I think this would occur if the test file is run directly, though going by the configuration I wouldn't expect that to happen.

Does debugging work through use VS Code's "debug terminal" feature?

There's a known issue where npx ava --version prints "unknown". No idea why it would print 0.1.0, maybe something is wrong somehow somewhere with that.

[Basssiiie]

Both "caught exceptions" and "uncaught exceptions" are unchecked. I removed all my other breakpoints as well but it still happens regardless of having breakpoints.

Using the Javascript Debug Terminal and running npx ava does work as expected though. :) (Though it runs through all files, but that's probably intended.)

[Basssiiie]

I know nothing about the internals of AVA but I did find this assert, and the refs it is importing is initialized as null in state.cjs. I don't see it being overwritten/changed in the code around it. Might that be something?

[novemberborn]

(Though it runs through all files, but that's probably intended.)

You can provide a specific test file as an argument.

I know nothing about the internals of AVA but I did find this assert, and the refs it is importing is initialized as null in state.cjs. I don't see it being overwritten/changed in the code around it. Might that be something?

It is the problem, but under normal execution it is supposed to be assigned. The question is why is that not happening.

[Basssiiie]

Alright thank you for your time. If you still need any more info regarding solving this issue, please let me know. :)

[ctjlewis]

Running into this, very weird. Running yarn add ava and then testing works, but after the second run I encounter the issue here.

refs.runnerChain remains null, and the Runner never starts and changes it. Version logs 0.0.1. My hunch is it has to do with Node module loader caching?

[novemberborn]

My hunch is it has to do with Node module loader caching?

Interesting hunch! Though the tests run in fresh worker threads so I wouldn't expect any caching to be in play. Does it work if you configure AVA with workerThreads: false?

[Basssiiie]

For me setting "workedThreads": false in the AVA config in package.json, or adding --workerThreads=false as a cmdline argument, did not work unfortunately. I still get the same error.

[johndeighan]

I am also encountering this error. Unfortunately, the only option that I have at this point is to stop using ava. I did try completely clearing the node module cache, after rebooting, and it didn't change a thing. I should add that I've been using ava 3 for quite some time now without problems, but I'm opposed to continuing to use a library once a new version is released. FYI, I've upgraded ALL instances of ava to version 4 so it's not a problem with mixing versions.

[ctjlewis]

I am also encountering this error. Unfortunately, the only option that I have at this point is to stop using ava. I did try completely clearing the node module cache, after rebooting, and it didn't change a thing.

I just ran into it again a few minutes ago.

It's a caching issue of some kind. rm -rf node_modules/ava && yarn add -D ava got me back to working state.

[novemberborn]

I can't reproduce this.

• AVA 4.0.1
• Node.js 17.6.0 (but not sure if VS Code inherits that)
• VS Code 1.65.0

I tried with a test.mjs and test.cjs file, as in the original post. Debug configuration from the original post.

I did not try with a TypeScript file to then make use of ts-node/register but I did load it. Version 10.7.0.

If somebody could share a project in which this is reproducible I can take another look.

[Basssiiie]

Unfortunate that you weren't able to reproduce it. I just made a new project with:

• AVA 4.0.1
• Node.js 17.6.0 (it was previously 16.11.1)
• VS Code 1.65.0
• TS-Node 10.7.0
• OS: Windows 10.0.19043 64-bit
• npm ava --version: 4.1.0

I did notice VS Code states it's using Node.js version 14.16.0 in the About window, but I don't know if that one is used for debugging as well. Update: running node --version VS Code debug task prints 17.6.0.

The project: ava-error-project.zip

It's nothing more than...

npm init
npm install ava ts-node -D

Plus the launch.json, AVA config in package.json and two test files.

The problem unfortunately still occurs in both Typescript and regular CJS files. It also occurs without TS-Node (after removing it). They all give:

[D:\ava-error-project/node_modules/.bin/ava.CMD]() [d:\ava-error-project\tests\javascript.cjs]()
Debugger attached.

  Uncaught exception in tests\javascript.cjs

  AssertionError [ERR_ASSERTION]: The expression evaluated to a falsy value:

    assert(refs.runnerChain)


  × tests\javascript.cjs exited with a non-zero exit code: 1
  ─

  1 uncaught exception
Waiting for the debugger to disconnect...

If it cannot be fixed, it seems I'll have to stay on version 3.x indefinitely.

[ctjlewis]

It's not surprising that you couldn't reproduce it because it's a nondeterministic bug.

Closing this issue is inappropriate but you're free to do it, though that would mean this software is no longer being actively maintained.