-
Notifications
You must be signed in to change notification settings - Fork 24
Description
Describe the bug
Test suite with react-hooks fails with
Test suite failed to run
Jest encountered an unexpected token
This usually means that you are trying to import a file which Jest cannot parse, e.g. it's not plain JavaScript.
By default, if Jest sees a Babel config, it will use that to transform your files, ignoring "node_modules".
Here's what you can do:
• If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/en/ecmascript-modules for how to enable it.
• To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config.
• If you need a custom transformation specify a "transform" option in your config.
• If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option.You'll find more details and examples of these config options in the docs:
https://jestjs.io/docs/en/configuration.htmlDetails:
(...)/node_modules/@capacitor-community/react-hooks/geolocation/index.js:1
({"Object.":function(module,exports,require,__dirname,__filename,global,jest){export * from './useGeolocation';
To Reproduce
Steps to reproduce the behavior:
- Create React app with create-react-app
- Create custom hook using useGeolocation
- Create test for custom hook
- Run npm test
- See error
Expected behavior
Test does not fail with compile error
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
- OS: macOS
- Browser terminal
- Version 11.2.2
Smartphone (please complete the following information):
- Device: [e.g. iPhone6]
- OS: [e.g. iOS8.1]
- Browser [e.g. stock browser, safari]
- Version [e.g. 22]
Additional context
Add any other context about the problem here.