Cleaned up package.json - removed stub scripts (test), named evolve/wiki build in a consistent way ([evolve/wiki][-less][-win]), added one script to build everything (build), added a script to deploy the game to GitHub pages. Added Windows versions of all scripts (with -win postfix). Updated the readme with new build commands and additional explanations for contributors.
The build in general is still a mess, because running index.html directly generally does not work due to CORS + trying to run evolve/evolve.js. So it is not possible (without any unusual adjustments in Google Chrome, at least) to run evolve directly. Therefore, I don't see the reason to keep compiled/minified files in the repo anymore, but I'll try to do something about that in future PRs.
Tested to work on Windows and Linux. The reason they are different is that Windows' rm and mkdir and cp either doesn't exist or has different arguments in Windows cmd or PowerShell. Perhaps using a node package to make it consistent and make a single, cross-platform script would be nice, but that's also for a future PR.
Cleaned up package.json - removed stub scripts (test), named evolve/wiki build in a consistent way ([evolve/wiki][-less][-win]), added one script to build everything (build), added a script to deploy the game to GitHub pages. Added Windows versions of all scripts (with -win postfix). Updated the readme with new build commands and additional explanations for contributors.
The build in general is still a mess, because running index.html directly generally does not work due to CORS + trying to run evolve/evolve.js. So it is not possible (without any unusual adjustments in Google Chrome, at least) to run evolve directly. Therefore, I don't see the reason to keep compiled/minified files in the repo anymore, but I'll try to do something about that in future PRs.
Tested to work on Windows and Linux. The reason they are different is that Windows' rm and mkdir and cp either doesn't exist or has different arguments in Windows cmd or PowerShell. Perhaps using a node package to make it consistent and make a single, cross-platform script would be nice, but that's also for a future PR.
This PR already contains #1054.