Search first

• I searched and no similar issues were found

What Happened?

When exporting even an empty graph, the resulting directory contains a static/ subdirectory, which takes a whooping 48 megabytes of Javascript, CSS files, and more. Surprisingly, the first place is taken not by a minified .js file or some fonts, but by main.css:

8326 KB - static/css/main.css
7033 KB - static/js/main.js 
5212 KB - static/css/fonts/tabler.icons.svg
4950 KB - static/js/tldraw.js.map
1929 KB - static/js/tabler.min.js
1315 KB - static/css/fonts/tabler.icons.eot
1315 KB - static/css/fonts/tabler.icons.ttf
 965 KB - static/js/code-editor.js
 831 KB - static/js/excalidraw.js
...

This CSS does get downloaded when you open the exported pages in your browser. Why is it so large? Does LogSeq even need all these 18+ MB to work in read-only mode?

Reproduce the Bug

• Create an empty graph
• Export it as HTML
• Host it with something like python -m http.server
• Open it in browser, run a network performance analysis
• Meditate on this cursed world of modern web applications that we've created

Expected Behavior

No response

Screenshots

Desktop or Mobile Platform Information

LogSeq 0.9.11

Additional Context

No response

Are you willing to submit a PR? If you know how to fix the bug.

• I'm willing to submit a PR (Thank you!)