Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

8.0.3 broken? Module jest-puppeteer should have "jest-preset.js" or "jest-preset.json" file at the root. #532

Closed
fregante opened this issue Mar 8, 2023 · 2 comments Β· Fixed by #533

Comments

@fregante
Copy link

fregante commented Mar 8, 2023

πŸ› Bug Report

Jest refuses to run due to an error in the preset

● Validation Error:

  Module jest-puppeteer should have "jest-preset.js" or "jest-preset.json" file at the root.

  Configuration Documentation:
  https://jestjs.io/docs/configuration

To Reproduce

npm init -y
npm install --save-dev jest-puppeteer puppeteer jest
echo '{"preset":"jest-puppeteer"}' > jest.config.json
npx jest

System:

  • OS: macOS 13.2.1
  • CPU: (16) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
  • Memory: 73.23 MB / 16.00 GB
  • Shell: 3.6.0 - /usr/local/bin/fish

Binaries:

  • Node: 18.13.0 - /usr/local/bin/node
  • Yarn: 1.22.11 - /usr/local/bin/yarn
  • npm: 9.6.0 - /usr/local/bin/npm

npmPackages:

  • jest-puppeteer: ^8.0.3 => 8.0.3
gregberge added a commit that referenced this issue Mar 8, 2023
gregberge added a commit that referenced this issue Mar 8, 2023
gregberge added a commit that referenced this issue Mar 8, 2023
@fregante
Copy link
Author

fregante commented Mar 8, 2023

It worked, thanks! I'll probably report more issues later (I'm updating some deps in fregante/webext-dynamic-content-scripts#56)

Screenshot 1

@christjt
Copy link

christjt commented Mar 8, 2023

@fregante I am also experiancing a bunch of chrome windows being sparned. Do you know any way to work around this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants