These two changes seem generally useful and worth contributing now, ahead of the other explorations around GitHub actions and workflows.
scripts/preview-package generates a node package tarball with a speculative semver version. The motivated developer can copy the tarball to a web server and npm install http://... the tarball.
There are two other places I have experimented with this kind of workflow:
the glitch wiki development experiment (and this in particular https://glitch.com/edit/#!/wiki-dev?path=build-wiki.sh)
using a wiki assets folder as a package repo for local experiments
scripts/scopify-package was created specifically for use with GitHub package registry. This is promoted into a script so it can be debugged and tested outside of GitHub actions.
These two changes seem generally useful and worth contributing now, ahead of the other explorations around GitHub actions and workflows.
scripts/preview-package generates a node package tarball with a speculative semver version. The motivated developer can copy the tarball to a web server and npm install http://... the tarball.
There are two other places I have experimented with this kind of workflow:
the glitch wiki development experiment (and this in particular https://glitch.com/edit/#!/wiki-dev?path=build-wiki.sh) using a wiki assets folder as a package repo for local experiments scripts/scopify-package was created specifically for use with GitHub package registry. This is promoted into a script so it can be debugged and tested outside of GitHub actions.
very similar to fedwiki/wiki-client/pull/269