You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What version of React, ReactDOM/React Native, Redux, and React Redux are you using?
React: 18.2.0
ReactDOM/React Native: RN 0.71.7
Redux: 4.2.1
React Redux: 8.0.7
What is the current behavior?
I'm trying to do a test with a component that is using useDispatch of react-redux. Then I create a Provider wrapper in order to be able to use redux in my tests but an error appears saying:
console.error
Warning: React.jsx: type is invalid -- expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports.
43 | it('should render the component and handle the finish stop logic', async () => {
44 | const {getByText} = render(
> 45 | <Provider store={store}>
| ^
46 | <FinishStop />
47 | </Provider>,
48 | );`
I have done a console.log of provider and the result is 'undefined' but the importation is right.
import {Provider} from 'react-redux';
I don't know if this is because of my config. Here you go my config files:
What version of React, ReactDOM/React Native, Redux, and React Redux are you using?
What is the current behavior?
I'm trying to do a test with a component that is using useDispatch of react-redux. Then I create a Provider wrapper in order to be able to use redux in my tests but an error appears saying:
I have done a console.log of provider and the result is 'undefined' but the importation is right.
import {Provider} from 'react-redux';
I don't know if this is because of my config. Here you go my config files:
babel.config.js
package.json
What is the expected behavior?
provider is undefined
Which browser and OS are affected by this issue?
No response
Did this work in previous versions of React Redux?
The text was updated successfully, but these errors were encountered: