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 }}
Repository navigation
Should we expose a high-level bundler module / CLI ? #768
.. so that users (not familiar with browserify or webpack) could make easily make their own custom plotly.js bundle. See discussion starting from #740 (comment)
Could just move the _bundle function to an export of a standalone repo. So then plotly.js requires plotly.js-bundler as a dev dependency. Does plotly.js-bundler require plotly.js as a dependency? (which wouldn't actually need a circular require, but it's still a little weird.)
Activity
rreusser commentedon Jul 22, 2016
Could just move the
_bundlefunction to an export of a standalone repo. So then plotly.js requires plotly.js-bundler as a dev dependency. Does plotly.js-bundler require plotly.js as a dependency? (which wouldn't actually need a circularrequire, but it's still a little weird.)etpinard commentedon Jul 22, 2016
I don't think so. We could make the default path to the plotly.js index
require.resolve('plotly.js')while letting users set their own path.If we go along that path, we should move the
compress_attributestransform to this new repo and add awatchify-powered--watchoption.etpinard commentedon Sep 14, 2018
Closing.
Between our partial "dist" npm packages (added in #2670) and our building instructions, I don't see this happening.
etpinard commentedon Sep 14, 2018
Also referencing #1584 which applies our compress attribute transform by default.