issue in package JSON

[kookma]

There are some typos in https://github.com/TheDiveO/ThirdFlow/blob/master/package.json
Which makes it fails on Windows system

Line 20 -26

    "start": "tiddlywiki editions/develop --verbose --server $npm_package_config_port $:/core/save/all text/plain text/html & echo $! > tw.pid",
    "stop": "kill `cat tw.pid` && rm tw.pid",
    "winstart": "start \"ThirdFlow Develop\" cmd /c tiddlywiki editions/develop --verbose --server %npm_package_config_port $:/core/save/all text/plain text/html",
    "winstop": "taskkill /fi \"WINDOWTITLE eq ThirdFlow Develop\"",
    "develop": "tiddlywiki editions/develop --verbose --server $npm_package_config_port $:/core/save/all text/plain text/html",
    "release": "tiddlywiki editions/release --verbose --build release",
    "test": "tiddlywiki editions/release --verbose"

for windows system environmental variable escaped with % % so in any of avobe command to be used on Windows, $npm_package_config_port shall change to %npm_package_config_port %

See also: https://stackoverflow.com/questions/39793500/how-to-use-variables-in-npm-scripts-on-windows

Please correct this also in TiddlywikiPluginSkleton.

[kookma]

Note:
I also recommend to use develop, release for all OS.

[thediveo]

Good catch! Thank you for that.

I have to admit that I don't spend any private time on Windows, so Windows only when my employer pays me for at my daytime job. And even there, most work nowadays happens in VMs, on remote CI chains, and on platform-agnostic web apps, because Windows causes so much unnecessary costs.

[kookma]

Thank you @thediveo
I would be happy to help whenever you like to test on Windows!
I use on daily basis this great plugin!

One more question

As I explained in another issue, ThirdFlow does not create the plugin.info
This is essential when you want to distribute the plugin as its source folder look at
https://tiddlywiki.com/dev/#Developing%20plugins%20using%20Node.js%20and%20GitHub

I would appreciate if ThirdFlow can create the plugin.info when one issues the npm run release

What do you think?