Don't pin the react and react-dom version and move react to peerDependencies

[smeng9]

We should always use the caret (^) symbol to specify the react version range in the package.json in a public library and let package manager to resolve to a single instance of react package.

The react and react-dom should be in the peerDependencies, because our project (we as a user) will install them. The duplicate instances of the package also increase the project size.

If we go to your npm package https://www.npmjs.com/package/@iwer/devui?activeTab=code and look for the build/iwer-devui.min.js you can find duplicate code of the react package.

Also duplication will cause hard to debug bugs in production as the context and hook used by one version of react is returning something, and the context and hook used by another version of react is returning a different thing.

See facebook/react#13991

[smeng9]

If r170 version of three.js is causing problem, maybe only three.js should be pinned? Even though this may still cause warnings that multiple three.js instances gets loaded.

[kwaa]

I think it is also necessary to move three to peerDependencies.

[smeng9]

@kwaa

@felixtrz 's previously decided to pin a specific version of three #6 (comment) due to a breaking change. If we move to peerDependency, we cannot ensure user installed the exact compatible version. What is your opinion?

[kwaa]

@felixtrz 's previously decided to pin a specific version of three #6 (comment) due to a breaking change. If we move to peerDependency, we cannot ensure user installed the exact compatible version. What is your opinion?

Compatible versions can be detected even if set to peer dependencies.

like this:

{
  "peerDependencies": {
    "react": ">=18.0",
    "react-dom": ">=18.0",
    "three": "<=0.168"
  }
}