Closed augustmuir closed 2 years ago
Switching to >=16.x
is fine, but there's no need to drop React 17. In order to support the next major version too, you actually still need to add it as an ||
So: >=16.x || ^17
@paintedbicycle great thanks ~ that fixes the parsing error for me.
Updated this pr to "react": ">=16.x || ^17"
54425d31dbe4c85407c4171449b45be338201ea4
Pull #89 uses
||
in version which results in the error below. Changed react version syntax from^16.x || ^17
to>=16.x
to fix this issue.