You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 3, 2024. It is now read-only.
I have a project that relies on dash-core-components (https://www.npmjs.com/package/dash-core-components). When upgrading the module from 1.8.0 to 1.10.1 and rebuilding my project, I get the following error:
ERROR in ./node_modules/dash-core-components/lib/utils/LazyLoader/plotly.js
Module not found: Error: Can't resolve 'plotly.js' in '/home/plotly/Workspace/{my_project}/node_modules/dash-core-components/lib/utils/LazyLoader' @ ./node_modules/dash-core-components/lib/utils/LazyLoader/plotly.js 9:42-11:14 @ ./node_modules/dash-core-components/lib/components/Graph.react.js @ ./src/lib/components/Graph.react.generated.js @ ./src/lib/index.js
I resolved the error by doing npm i --save plotly.js in my project. I suspect this error arose from moving the plotly.js dependency from dependencies to devDependencies in this repo's package.json in PR #800. Was the move to devDependencies intentional @Marc-Andre-Rivet or can we safely move it back?
For now, I can simply take on the plotly.js dependency in my own project's package.json.
The text was updated successfully, but these errors were encountered:
I have a project that relies on
dash-core-components
(https://www.npmjs.com/package/dash-core-components). When upgrading the module from1.8.0
to1.10.1
and rebuilding my project, I get the following error:I resolved the error by doing
npm i --save plotly.js
in my project. I suspect this error arose from moving theplotly.js
dependency fromdependencies
todevDependencies
in this repo'spackage.json
in PR #800. Was the move todevDependencies
intentional @Marc-Andre-Rivet or can we safely move it back?For now, I can simply take on the plotly.js dependency in my own project's
package.json
.The text was updated successfully, but these errors were encountered: