bug: TypeError: (0 , _dom.getConfig) is not a function
See original GitHub issue@testing-library/user-event
version: 12.0.9- Testing Framework and version: React Testing Library v10.4.3
- jest: v26.1.0
- DOM Environment: jsdom v16 (default one from jest)
What you did: I just bumped user-event from 12.0.7 to 12.0.9
What happened:
I’m getting TypeError: (0 , _dom.getConfig) is not a function
when using userEvent.click
in tests that were passing using v12.0.7
Issue Analytics
- State:
- Created 3 years ago
- Reactions:4
- Comments:6 (5 by maintainers)
Top Results From Across the Web
TypeError: (0 , _react.useEffect) is not a function - Stack Overflow
The only solution I've found that works are if I import it like so: import React from 'react'; const X = () =>...
Read more >User-event, Npm @testing-library/user-event, FireEvent vs ...
This is a light wrapper around the react-dom/test-utils act function. All it does is forward all ... Typeerror: (0 , _dom.getconfig) is not...
Read more >'X' is not a function TypeError in React [Solved] | bobbyhadz
The React.js Uncaught TypeError: X is not a function occurs when we try to call a value that is not a function as...
Read more >uncaught typeerror: (0 , react__ ...
When trying to edit a record I get the Error "navigator.block is not a function". Steps to reproduce: 1- User the Form Component...
Read more >React, how to fix the TypeError: resolver is not a function error
Turned out the solution was very simple. So, make sure you have a default export and the error will go away.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Could this error be updated to better indicate the fix ?
We’ve added it to the installation instructions recently