Closed kwonoj closed 4 years ago
current package.json's uuid
version is 7.0.1 which have export to v5
, FYI.
I deleted & retry whole extension cache / project's node_modules both but didn't work still.
Could you please try updating your project to use our automatic configuration feature for Jest v24+? Automatic configuration uses the Jest runtime instead of Wallaby runtime so this may fix your problem.
In the meantime, we'll start reviewing your logs.
We've identified the cause of your problem and this has been fixed in Wallaby core v1.0.911. The issue was specific to jest and did not affect jest when using automatic configuration.
Wallaby should automatically update for you. If not, you may force an immediate update using the VS Code command, Wallaby.js: Force Core Update
.
Unless you have a good reason to keep your wallaby.js
configuration file, we also recommend switching to using Automatic Configuration. This should be as simple as:
jest.json
to jest.config.js
and add module.exports =
at the start of the filewallaby.js
fileWallaby.js: Selection Configuration
and select Automatic Configuration <project directory>
.
Issue description or question
For some reason, wallaby imports module
uuid
from its extension path instead of project'snode_modules
which fails up test cases due to providing different version than project's pkg.for other modules in pkg, it pulls properly from pkg's node_modules:![image](https://user-images.githubusercontent.com/1210596/84958621-9cd39280-b0b2-11ea-997c-62752f9d2958.png)
I tried to create repro case but failed, somehow new project I created does not have this problem.
//jest.json
//wallaby.js
There was no specific mock to
uuid
module itself.Wallaby diagnostics report