No compatibility with new react 18

[bsjaramillo]

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: solesesteluquis@0.1.0
npm ERR! Found: react@18.0.0
npm ERR! node_modules/react
npm ERR! react@"^18.0.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^16.8.1 || ^17" from react-alert@7.0.3
npm ERR! node_modules/react-alert
npm ERR! react-alert@"*" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

[Blaumaus]

Fixed it at #191

[Blaumaus]

@bsjaramillo also until it's merged you can try out it's fork with the React 18 support - https://www.npmjs.com/package/@blaumaus/react-alert

[mdodge-ecgrow]

All of a sudden on my latest deployment, I am getting a nasty error from this library. Any ideas what would be causing this?

Uncaught Error: Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://fb.me/react-invalid-hook-call for tips about how to debug and fix this problem.
    React 2
    useTheme useTheme.js:4
    useStyles makeStyles.js:222
    WithStyles withStyles.js:55
    React 14

[mdodge-ecgrow]

I couldn't figure out that error and was under a time crunch. I have switched over to https://github.com/fkhadra/react-toastify . That package seems to be much better maintained.

[borm]

hook.js:608 Warning: Provider2: Support for defaultProps will be removed from function components in a future major release. Use JavaScript default parameters instead. Error Component Stack