When you use TiddlyWiki on node.js, you essentially have two copies of TiddlyWiki running. One in the browser, one in node.js (server component), and the two synchronize with each other. The browser copy is responsible for the UI/UX and the node.js copy handles the API and saving and loading the tiddlers from disk. This is a very simplified explanation but hopefully it gets the point across.
Most plugins only involve the UI/UX in the browser and therefore do not need to run under node.js. However, plugins that need to tweak the behaviour of the wiki running under node.js (the server component) can need to be executed under node.js to ensure they operate properly and are executed in the correct order, and therefore need to be installed as a plugin folder. Cheers, Saq On Friday, September 11, 2020 at 7:17:37 AM UTC+2, Tejasvi S Tomar wrote: > > Note that including a plugin as an ordinary tiddler (e.g. by dragging and >> dropping a plugin into the browser) will result in the plugin only being >> active in the browser, and not available under Node.js. > > > https://tiddlywiki.com/static/Installing%2520custom%2520plugins%2520on%2520Node.js.html > > Why the plugin being "available under Node.js" is relevant as long as it > works in the browser? > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/3482ceff-aac3-4a37-8f45-a0e036d7a5e5o%40googlegroups.com.
