Support exporting server plugins.

[rryan]

Is it possible to compile and output a plugin in the format expected by TiddlyWiki when serving via Node.js?

https://tiddlywiki.com/static/PluginFolders.html

I may have missed it, but npm run build:library outputs JSON files, which I can't figure out how to load in my Node.js environment.

Thanks for Modern.TiddlyDev, by the way! It has been very useful for developing TypeScript-based plugins.

[linonetwo]

Hi, sorry for delay, no one subscribed to the issue of this repo, so no one response for a while. you can @ me at any time when no response.

When using the Node.js version of TiddlyWiki:

1. Using JSON format of the plugin is correct.
2. Using a folder structure of the plugin is incorrect.

See：https://talk.tiddlywiki.org/t/plugins-on-nodejs/14912/4?u=linonetwo

Simple answer:

1. drag & drop from plugin demo site
2. install from plugin library or CPL

Long answer:

https://talk.tiddlywiki.org/t/installing-plugins-on-tiddlywiki-node-js-help-for-better-documentation/1158/20?u=linonetwo

Just come across this again via google search, so I answer this again:

1th of all, recommend my tiddlywiki app https://github.com/tiddly-gittly/TidGi-Desktop , which is an opensourced Obsidian alternative, where all plugins are installed via clicking "Install" button.
It starts a nodejs tiddlywiki instance, but you can choose enable or disable http server, so protect privacy even in open wifi area.

And secondly:

Don’t put plugins to pligin folder & update tiddlywiki.info, it is not recommended.

Recommended way is drag & drop or click Install button on CPL.

As a plugin author and nodejs wiki user myself, I never recommend people to modify json config file manually or put files into folder manually, it will scare many valuable new users out of tw community.

Recommended on CPL and our chinese tutorial , based on discussion

We care about user growth and new user experiences.

https://talk.tiddlywiki.org/t/relink-plugin-installation-on-node-js-tw/12998/12?u=linonetwo

[linonetwo]

But the consideration above is totally out of user-friendly. because historically, many people continue to have trouble upgrading and maintaining folder-based plugins.

As tiddlywiki more become L2 memory layer of LLM, I think that won't be a big problem anymore, people can just use a LLM agent to check for updates, download the latest folder, and move it to the plugin folder. If you use strong advice, I can send a copilot agent to implement this feature: compile the whole folder as is, and zip it in the Github release.