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
Plotly was chosen because of its ease of use, and that it works great. However, it is HUGE!
So lets code-split, right?
I had a slash at that now with Svelte and it seems to work. However, now it flickers a lot when the chart-component is receiving props. Probably because it recreates the whole import, in addition to the async-importer. Now, this could probably be solved.
However, it is apparant that Plotly at the moment does not tree-shake. I have not checked yet if they support tree-shaking at all, but I guess its should work if we make the import-paths more specific.
Also, the code-module with yaml-support is a bit big. Maybe we should go for a different yaml-library? Or why bother, we already have toml and json, so yaml is kind of redundant.
The text was updated successfully, but these errors were encountered:
Plotly was chosen because of its ease of use, and that it works great. However, it is HUGE!
So lets code-split, right?
I had a slash at that now with Svelte and it seems to work. However, now it flickers a lot when the chart-component is receiving props. Probably because it recreates the whole import, in addition to the async-importer. Now, this could probably be solved.
However, it is apparant that Plotly at the moment does not tree-shake. I have not checked yet if they support tree-shaking at all, but I guess its should work if we make the import-paths more specific.
Also, the code-module with yaml-support is a bit big. Maybe we should go for a different yaml-library? Or why bother, we already have toml and json, so yaml is kind of redundant.
The text was updated successfully, but these errors were encountered: