Hi,
I'm facing an issue with plotly.js and yarn.
yarn add plotly.js
yarn add v1.12.3
info No lockfile found.
warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json.
[1/4] Resolving packages...
warning plotly.js > regl-splom > [email protected]: use String.prototype.padStart()
warning plotly.js > ndarray-fill > cwise > static-module > through2 > xtend > [email protected]:
warning plotly.js > point-cluster > bubleify > buble > [email protected]: This is not needed anymore. Use require('os').homedir() instead.
error Couldn't find package "3d-view@^2.0.0" required by "gl-plot3d@^2.4.2" on the "npm" registry.
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.
Any hint to solve it?
Many thanks
Yes I'm facing this issue too since yesterday
Even I am facing the same with npm
I suspect this commit https://github.com/plotly/plotly.js/commit/4a4bdea15a5e204f373303a1c81ee32ddc66da09
I suspect this commit 4a4bdea
Could you please explain why?
Even I am facing the same with npm
@pareshbbb to help debug, would you mind posting npm error logs?
https://status.npmjs.org/incidents/lvgmcrfvrvsh there are some incidents with npm hmm
https://status.npmjs.org/incidents/lvgmcrfvrvsh
We are currently investigating issues with installing certain packages.
Some of the packages known to be affected are: 3d-view, error-ex ,42-cent-base, 8base-cli.
Yes i am facing the same issue trying to install plotly 1.49.0
Update:

there is a workaround for this which worked for me, in your package.json
set the following
```
"resolutions": {
"3d-view": "git://github.com/mikolalysenko/3d-view.git#017651d48ac7b42e81447adb1a2e06a4972b3293"
}
Another update:


The issue now appears fixed. I was able to get a fresh yarn add plotly.js to work. Closing.
Most helpful comment
https://status.npmjs.org/incidents/lvgmcrfvrvsh there are some incidents with npm hmm