Hi @naina-lele
This seems to be a bug in npm related to peer dependencies.
npm
See my comment on a related thread for a workaround: