$:/core/save/lazy-all overwrite or clone?

#1

Can I overwrite $:/core/save/lazy-all or clone a $:/core/save/lazy-all+images to allow non system images to be saved and utilize that for the root-tiddler at start up? I am looking to avoid the image tiddler load time for 500k of icons while still gaining lazy load benefits for 75mbs of text tiddlers and echarts.

example $:core/save/lazy-all+images maybe:

\define saveTiddlerFilter()
[is[system]] -[prefix[$:/state/popup/]] -[[$:/HistoryList]] -[[$:/boot/boot.css]] -[type[application/javascript]library[yes]] -[[$:/boot/boot.js]] -[[$:/boot/bootprefix.js]] [is[tiddler]type[application/javascript]] [!is[system]is[image]] +[sort[title]] 
\end
\define skinnySaveTiddlerFilter()
[!is[system]] -[type[application/javascript]] -[!is[system]is[image]]
\end
{{$:/core/templates/tiddlywiki5.html}}
Lazy-all performance
#2

I think you will be better off cloning rather than overwriting.

Your filters look good to me. I don’t have experience with lazy saving, so I suggest you test it carefully and see if it works and meets your needs.

#3

Thanks, still learning the nodejs world and wanted someone to encourage me to have a go. I’ll set up a test server and see what I can break.