Broken npm publish

[HoloTheDrunk]

Example of a failing publish

Expected Behavior

The CI should successfully publish the iTowns package.

Actual Behavior

The CI fails at the linking step on Three.js peer dependencies.

Possible Cause/Fix/Solution

The actual errors points out a missing Three.js dependency of both version 0.174.0 and 0.170.0 (the latter seemingly being from the previous patch release). This behaviour is a bit surprising and I'm not sure why it's checking the previous version's dependencies nor why a "^0.170.0" dependency is not satisfied by a "^0.174.0".

[jailln]

I just saw that @gchoqueux opened #2515 on this. Are you still working on it @gchoqueux ? Do you have any leads ?

[gchoqueux]

I worked on issue #2515, but it seems to be a different problem. In #2515, the publishing fails when using "publish next after release." It's very difficult to fix because it works locally.

The three 0.170.0 dependency comes from the Three.js 3D Tiles renderer — see package-lock.json.