Open ackvf opened 2 years ago
When I tried to change the config.paths.root + "/jest.config.js"
by hand to jest.config.ts
it didn't really help. It did discover the files, but then I received
FAIL Contracts test/Example.ts
● Test suite failed to run
Jest encountered an unexpected token
Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax.
Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration.
I am getting this error while trying to run
hardhat test:jest
on windows.But then when I run
npx jest --showConfig
it does read myjest.config.ts
correctly, which can be seen from the output:This is my
jest.config.ts
What I am finding odd is the weird forward slash where it should have been a backwards slash. And then it actually tries to load
jest.config.js
instead of.ts
What should I do?