Closed arnaudvergnet closed 2 years ago
Thanks. We already updated the project dependencies, but It might need a new release.
I've just pushed version 4.0.0-RC.1. Can you confirm it fixes the problem?
I tried installing yarn 4.0.0-RC.1
, but there doesn't seem to be such a version available in the registry
We are checking on it. There seems to be a problem in the repo
We've republished version 4.0.0-rc.0
(lowercase rc), and it seems to fix the problem on our side. Sorry for that, but I didn't know that npm was case sensitive concerning releases.
Tried with 4.0.0-rc.0
and it fixes on my side as well.
Thanks, closing the issue.
What you were expecting: Specifying
"react-admin": "4.0.0-RC.0"
inpackage.json
should install the 4.0.0-RC.0 for react admin and related packages (ra-ui-materialui
and others).What happened instead: Specifying
"react-admin": "4.0.0-RC.0"
inpackage.json
installs the 4.0.0-RC.0 for react admin but the 4.0.0-beta.3 for related packages (ra-ui-materialui
and others).Steps to reproduce:
"react-admin": "4.0.0-RC.0"
inpackage.json
yarn
package.json
forra-ui-materialui
Other information:
Specifying
"react-admin": "^4.0.0-RC.0"
inpackage.json
(note the ^) installs the 4.0.0-beta.3 for react admin and related packages.In react-admin's package.json versions are written with this symbol so this is what is causing this issue.
My guess is yarn has trouble understanding the RC.0 version name. Maybe making it lowercase would help?
I also think versions should not use ~ or ^ inside of react-admin's
package.json
. This would ensure all components are exactly at the same version as react-admin main package.Environment