But: is there another way ot hack to get the require working as needed? One bad idea that occured to me is simply adding an alias to $tw.modules.titles... Any better ideas?
Best regards,
TheDiveO--
You received this message because you are subscribed to the Google Groups "TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+...@googlegroups.com.
To post to this group, send email to tiddl...@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/1e9464ca-fbda-40c7-aeed-8c147ca95260%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
thank you very much for your answer. Being able to have a utility function that allows to load a JS module with a caller-supplied require() context or similar looks appealing. This would keep "aliasing" or dedicated module name resolution local to such modules that need it. And it would be cleaner than mucking around with $tw.modules.
Best regards,
TheDiveO--
You received this message because you are subscribed to the Google Groups "TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+...@googlegroups.com.
To post to this group, send email to tiddl...@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/cc5ea6e7-81a7-4d6d-99cb-4bb206219b40%40googlegroups.com.
One thing I noticed is related instead to using the getTiddlersFiltered wikimethod in a startup module. I only could get this going without throwing exceptions about missing bits and pieces after declaring my startup module to be run "after: startup". That's the kind of seemingly self-contradicting code I really like.
I have no idea why the jasemine startup module you pointed me to doesn't seem to have this issue.
Best regards,
TheDiveO