You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Previously working (~1 week ago) tests using vitest (both 0.18.0 and 0.19.0) seem to now fail with the message:
Runtime error: TypeError: Cannot set properties of undefined (setting '0')
In a different repo, I noticed setting '0' was replaced with the sequential order of the tests in the file (setting 1000001 for the first test 1000002 for the second etc). Upgraded vitest to latest (0.19.0) and force updated Wallaby core to verify, across two different machines.
At the moment we don't support root setting, to get the repo working please delete the settings from vitest.config.ts file. We'll be implementing support of the setting today or tomorrow.
Issue description or question
Previously working (~1 week ago) tests using vitest (both 0.18.0 and 0.19.0) seem to now fail with the message:
In a different repo, I noticed
setting '0'
was replaced with the sequential order of the tests in the file (setting 1000001
for the first test 1000002 for the second etc). Upgraded vitest to latest (0.19.0) and force updated Wallaby core to verify, across two different machines.Example failing repo - main branch here - /~https://github.com/ably-labs/react-hooks
Tests all pass using
npx vitest run
Wallaby diagnostics report
The text was updated successfully, but these errors were encountered: