I had this question as well and I think the answer is yes. I had conflicts with minor versions of rxjs (lots of type errors):
A depends on rxjs
A depends on B
B depends on rxjs
This would often result in two slightly different versions of rxjs being installed. So I tried this:
A depends on rxjs
A depends on B
B peer depends on rxjs
But when running tests etc for component B it was complaining that rxjs wasn't installed, so now I have:
A depends on rxjs
A depends on B
B depends on rxjs
B peer depends on rxjs
Works so far. The weird thing was that the version specification for rxjs in both projects would have allowed the same (latest) version of the library to be installed but npm/yarn still ended up installing two different copies.