If I try to build the single file HTML version from the Node.JS version via the “build” command will these global/local plugins be bundled in or will they be excluded leaving the end result missing plugins/functionalities?
The follow up question is: if the above worked and I then unpack the single file HTML version via the “load” command to a new Node.JS instance/location, will those plugin be unpacked into respective global/local plugin directories?
If your Node.js instance will use the plugins, the single file wiki will have them too.
They will not be unpacked. They are handled as data tiddlers, where one tiddler contains one plugin.
What exactly do you try to achieve?
I have an environment where I can run node.js and another where I can only run single html version. I’d like to be able to update one from the other: it’s fine to drop the target environment and recreate from the source, but it should work either direction, i.e. to recreate single html version from node.js version or the other way round.
Per this thread when using the node.js version, official plugins go into a separate folder in the node.js while other plugins should be installed via drag and drop.
If I start with node.js copy 1 with official plugins in separate folder to generate single html copy 2, and then use the single html copy 2 to unpack(“load”) into new node.js copy 3, where will the official plugins be stored? Is it reasonable to expect that a full directory comparison between node.js copy 1 and node.js copy 3 to be identical?