Optional Peer Dependencies report conflicts

[alex-moon]

Description

A fresh install of 3d-tiles-renderer fails due to failing dependencies.

Expected: 3d-tiles-renderer installs.

Actual:

npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/react
npm error   peer react@"*" from [email protected]
npm error   node_modules/expo
npm error     peerOptional expo@">=43.0" from @react-three/[email protected]
npm error     node_modules/@react-three/fiber
npm error       peerOptional @react-three/fiber@"^8.17.9" from [email protected]
npm error       node_modules/3d-tiles-renderer
npm error         3d-tiles-renderer@"*" from the root project
npm error     peer expo@"*" from @expo/[email protected]
npm error     node_modules/@expo/dom-webview
npm error       peerOptional @expo/dom-webview@"*" from [email protected]
npm error     3 more (expo-asset, expo-file-system, expo-gl)
npm error   peer react@"*" from @expo/[email protected]
npm error   node_modules/@expo/dom-webview
npm error     peerOptional @expo/dom-webview@"*" from [email protected]
npm error   5 more (react-native, react-native-webview, expo-asset, expo-gl, react-native-web)
npm error
npm error Could not resolve dependency:
npm error peerOptional react@"^18.3.1" from [email protected]
npm error node_modules/3d-tiles-renderer
npm error   3d-tiles-renderer@"*" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.

Reproduction steps

1. npm install 3d-tiles-renderer

Code

// code goes here

Live example

Screenshots & Tile Set

No response

Library Version

n/a

Three.js Version

n/a

[gkjohnson]

Thanks! I didn't realize this. Would you like to make a PR to help fix some of the conflicting dependencies up?

[gkjohnson]

I've created https://github.com/npm/cli/issues/8416 to try to understand what's going on here. The dependencies are otherwise not conflicting. In the meantime the package can be installed using --force.

[gkjohnson]

I've just published v0.4.12 with the changes from #1190 which seems to fix the issue but if what I've outlined in https://github.com/npm/cli/issues/8416#issuecomment-3040510099 is true then this will potentially break again when a new major release of react (or any of the optional dependencies that resolve to a later major version) is published. Hopefully this can be fixed in npm.