Open swa-desmat opened 4 months ago
Thanks for letting me know about this. Are you on Windows? I just checked and looks like the file paths are detected wrong on Windows (back- vs forward-slashes).
I pushed a new version (1.0.2) so hopefully that fixes it for you.
Hi @PoffM , thanks for your answer. I'm currently working on Mac Ventura 13.6.1. Unfortunately same issue, my jest.config.ts file isn't detected.
Information about VS Code: Version: 1.89.1 (Universal) Commit: dc96b837cf6bb4af9cd736aa3af08cf8279f7685 Date: 2024-05-07T05:14:24.611Z Electron: 28.2.8 ElectronBuildId: 27744544 Chromium: 120.0.6099.291 Node.js: 18.18.2 V8: 12.0.267.19-electron.0 OS: Darwin arm64 22.6.0
let me know if I can make some additional tests on my side to help you.
I don't have a Mac so can't verify myself if the config detection ever worked on it (though the detection works running the CI tests in macos).
Other guesses I have:
Hi @PoffM , the jest.config.ts file is located in the top level of the project.
I'll see if I can do the same test in another project and on a colleague's Mac. I'll let you know as soon as I've done these tests.
I just pushed another version (1.0.3) to improve the Jest config file handling.
Disabled the type-checking that could sometimes throw an error when parsing the config.
I'm not sure if this will fix it for your case though. It's a VSCode extension that interops with the user's test code, which I've found is tough to do because different projects will have differences that are hard for the extension code to anticipate.
Thanks, it's seems now good, the file is now well detected. I've another issue when I run the Visual test:
Jest: Failed to parse the TypeScript config file jest.config.ts TypeError: Invalid host defined options
I'm checking on my side, I found some post relative with Prettier.
``Good morning, I figure out an issue after installing the extension.
I've the error message: No Jest config found
A jest.config.ts file is existing in my project.
Package: