On single file wikis we have the tinka plugin packer.
Perhaps you could identify some methods to simplify your plugin builds at
this software layer instead.
Be warned the packer removes the standard tiddlers as it packs.
Also I do not know what the ultimate impact on node plugin tiddlers are.
Regards
Tony
On Thursday, September 19, 2019 at 5:02:30 PM UTC+10, Sebastian Ovide wrote:
>
> Hello
>
> I've working on a plugin and not sure if is there a better way of dealing
> with the dev cycle. Here is what I do
>
> 1) change the code
> 2) build
> 3) run the server ("--listen") with ++myuplugin
>
> everytime I change the code I need to do it all again.
>
> "scripts": {
> "test": "npm run build",
> "build": "npm run build:prepare && npm run build:TW",
> "build:prepare":
> "mkdir -p build/ && cp node_modules/tiddlywiki/editions/server/
> tiddlywiki.info build/ && node bin/updateVersion.js",
> "build:TW":
> "tiddlywiki ++./plugin build --verbose --output build/gh-pages/ --build index"
> ,
> "serve": "npm run build && (sleep 2 && open-cli http://127.0.0.1:8080
> --background) && tiddlywiki ++./plugin build --verbose --listen"
> },
>
> Is there a better way ? something that would build and refresh the browser
> if I change any code in the plug in? perhaps can tiddlywiki --listen support
> some kind of file watcher ?
>
> thanks
>
--
You received this message because you are subscribed to the Google Groups
"TiddlyWikiDev" 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/tiddlywikidev/891e2edb-b52b-4324-b7ed-de5ae8db39c3%40googlegroups.com.
