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
I am unable to run any test, I get the following error when calling createDOM():
Error: Cannot find module '/@builder.io/qwik/build' imported from '<absolute_path_to>/node_modules/.pnpm/@builder.io+qwik@1.1.5_undici@5.22.1/node_modules/@builder.io/qwik/core.mjs'.
- If you rely on tsconfig.json to resolve modules, please install "vite-tsconfig-paths" plugin to handle module resolution.
- Make sure you don't have relative aliases in your Vitest config. Use absolute paths instead. Read more: https://vitest.dev/guide/common-errors
❯ node_modules/.pnpm/@builder.io+qwik@1.1.5_undici@5.22.1/node_modules/@builder.io/qwik/core.mjs:1:31
1| /**
2| * @license
3| * @builder.io/qwik 1.1.5
| ^
4| * Copyright Builder.io, Inc. All Rights Reserved.
5| * Use of this source code is governed by an MIT-style license that can be
❯ tests/MyComponent.spec.tsx:1:31
StackBlitz seems to think I am using npm even though I am actually using pnpm. You will probably need to delete both package-lock.json and pnpm-lock.yaml and then run pnpm install.
Latest version of Vitest introduced breaking change which is something related to inline deps. Vitest 0.31.2 or something had the same issue then they fixed it and now latest version they decided to make it as a breaking change
Which component is affected?
Qwik Runtime
Describe the bug
I am unable to run any test, I get the following error when calling
createDOM()
:Reproduction
https://stackblitz.com/github/devatina11yb/qwik-testing
Steps to reproduce
StackBlitz seems to think I am using npm even though I am actually using pnpm. You will probably need to delete both
package-lock.json
andpnpm-lock.yaml
and then runpnpm install
.pnpm install
pnpm run test
System Info
Additional Information
I also tried with npm and I get the exact same error so it doesn't seem to be related to pnpm.
The text was updated successfully, but these errors were encountered: