Thanks. I will take a look. This is my first serious attempt at creating a plugin, and while it’s working reasonably well, there are three pain points. I’m wondering if this would fix them?
-
(minor) When I change the version, I need to keep it in sync between
package.json
andplugin.info
. I’m sure I could script this easily enough. -
(medium) I haven’t yet got a working GitHub Action, so I have to build, then push. I’d rather just push and have the build run on the GH side. This is not huge, but is a minor annoyance. I’m not particularly experienced with GH Actions, so while I was able to do this easily at work with Gitlab, my first two attempts here failed and I put it aside for the moment.
-
(major) Before I build, I need to manually move any changed plugin files from
/tiddlers
toplugins/myplugin
. This is not difficult to do, and if I keep with this solution, I will find a way to automate it in my build. But it feels very wrong.
There is also one feature I really love in this workflow: I build not just the main demo but also a copy in a version-specific folder. So while this plugin is simply hosted on GH Pages, I also have older versions kept handy. I need to do nothing more to create this new version than update the version number in package.json
(but see #1 above!) While this does not make GH releases, I don’t know whether I really care, as I expect the main distribution for a TW plugin to be an actual wiki, as in my demo.
Does this tool do something similar, that is, hosting older versions in demo pages?