adding create-data-dir batch file for windows

[huaigulin]

Description of proposed changes

This pull request can make installation on Windows much easier. It adds a Windows batch .bat file, which is Windows' equivalent of .sh script in Linux.

The only reason that npm install --global . fails in Windows is that Windows cannot execute Linux shell script and therefore does not support env command used in create-data-dir in package.json.

After taking a look at create-data-dir.sh, I think all it does is just creating two empty directories. Therefore we can write a .bat file to create those directories in Windows. And the npm install --global . command will succeed, without needing to create a Linux subsystem.

Related issue(s)

Fixes #
Related to #1100

Testing

For testing, I changed the create-data-dir command of package.json in my local environment to ".\\scripts\\create-data-dir.bat". Note that Windows directory separator is \ and has to be escaped in package.json, hence we see the weird-looking \\.

After changing create-data-dir command, npm install --global . ran successfully in Windows Powershell without npm errors:

(auspice) PS C:\...\auspice> npm install --global .
npm WARN deprecated fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
C:\...\.conda\envs\auspice\auspice -> C:\...\.conda\envs\auspice\node_modules\auspice\auspice.js

> auspice@2.16.0 postinstall C:\...\.conda\envs\auspice\node_modules\auspice
> npm run create-data-dir


> auspice@2.16.0 create-data-dir C:\...\.conda\envs\auspice\node_modules\auspice
> .\scripts\create-data-dir.bat


C:\...\.conda\envs\auspice\node_modules\auspice>if not exist data (
echo "Creating empty data directory"
 mkdir data
)
"Creating empty data directory"

C:\...\.conda\envs\auspice\node_modules\auspice>if not exist narratives (
echo "Creating empty narratives directory"
 mkdir narratives
)
"Creating empty narratives directory"
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.1.2 (node_modules\auspice\node_modules\chokidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.2.7 (node_modules\auspice\node_modules\watchpack-chokidar2\node_modules\chokidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN react-addons-css-transition-group@15.6.2 requires a peer of react@^15.4.2 but none is installed. You must install peer dependencies yourself.
npm WARN react-hot-loader@4.12.21 requires a peer of @types/react@^15.0.0 || ^16.0.0 but none is installed. You must install peer dependencies yourself.

+ auspice@2.16.0
updated 1 package in 5.884s

The two empty directories were also successfully created:

Next Step

We could simply update installation instructions to let Windows users know how to change package.json and then run npm install --global .. A more advanced/automated solution would be detecting OS then running the corresponding type of script.

Thank you for contributing to Nextstrain!

[huaigulin]

I can also help creating batch file for other shell scripts, like get-data.sh etc.