I utilize a large number of tiddlers tagged ChartData with type set to application/javascript to generate Echarts. I was surprised to find that these tiddlers are not being lazy loaded. Is this by design?
Apparently it is by design. If I override save-lazy-all.tid with the following L7 change will i potentially break stuff?
[!is[system]] -[type[application/javascript]!tag[ChartData]]
Guess I would also need similar tweak to line 4.
Hi @john.edw_gmail.com the core doesn’t currently support dynamic loading of JS modules.
It doesn’t prevent it, either. The core works on the assumption that module tiddlers are all loaded upfront because that simplifies the overall architecture.
You may be able to make something work, particularly if you are dealing with custom module types that you can load via explicit “require()” calls.
Apparently I misunderstood the various Echart data tiddler options and could have avoided marking the 15,830 tiddlers tagged ChartData as type application/javascript since I am displaying static charts generated upstream via my python script.
Believe that is a quick fix with @TW_Tones batch-functions and <$action-setfield $field="type" $value="vnd.tiddlywiki"/>.
Hopefully that will get me back to the skinny initial load I remember.
2 Likes