issue and workaround for react-dom as a peer dependency (yarn 2 with workspaces)

When using this package with yarn v2 (yarn berry), it throws while building:

Module not found: Error: use-context-selector tried to access react-dom (a peer dependency) but it isn't provided by its ancestors; this makes the require call ambiguous and unsound.

this error comes after resolving #134 by adding scheduler as a dependency 😉 (resolving this error is a bit easier than #134 - so I created another issue, hope this is fine for you)

You depend on use-context-selector, and they declared react-dom as a peerDependency. So you should also add react-dom to your peerDependencies to make sure, it is available.

workaround at the moment

Currently workaround is adding this to .yarnrc.yml

packageExtensions:
  jotai@*:
    peerDependencies:
      "react-dom": "*"

info about packageExtensions:

Some packages may have been specified incorrectly with regard to their dependencies - for example with one dependency being missing, causing Yarn to refuse it the access. The packageExtensions fields offer a way to extend the existing package definitions with additional information.

https://yarnpkg.com/configuration/yarnrc#packageExtensions

[dai-shi]

So, for now our recommendation is the workaround described in https://github.com/pmndrs/jotai/issues/135#issue-723129121

packageExtensions:
  jotai@*:
    peerDependencies:
      "react-dom": "*"

or the one described in https://github.com/pmndrs/jotai/pull/139#issuecomment-710701325

  "dependencies": {
    "react": "^16.14.0",
    "react-dom": "^16.14.0"
  },

[dai-shi]

TL;DR: If you write a package that depends on Foo, and if Foo has a peer dependency, then you must provide it in either of the dependencies or peerDependencies fields. You won’t “implicitly inherit” the peer dependencies declared in Foo.

Alright, I wasn’t aware this. Thanks for noting.