Create build scripts

[sukus21]

Hi there 👋

First of all, super cool little engine you got here, I'm very impressed! I fell down the js13k rabbit hole the other day, and found this engine thanks to the "resources" section on the website.

Snooping around the repository for a bit, I noticed the lack of build instructions. It is also not clear which parts of the source are stripped out of the lite version, or how the minification (of JS and/or GLSL) or zipping is done. I did some guesswork, and arrived at some results that are close enough.

So what we have here is a build script, that runs the code through terser, and then manually minifies the shader code using a series of regular expressions.

I have a few ideas for how to decrease the byte size of the engine even further, but in order to properly test if they save space when zipped or not, I needed a base to work from.

I'm looking forward to hearing your feedback :)

Notes:

• The zipped files are larger than the old ones, since they were a couple revisions out of date
• The logic to check for plugins gets evaluated at compile time thanks to terser, so those checks are completely free in terms of byte cost

[xem]

Hi and thank you for your message!
Glad that you enjoyed js13kgames. Have you seen the entries made with W.js ?
As you can see, a previous PR also attempts to automate the build but the person stopped responding.
Regarding the difference between normal and lite, the homepage (https://xem.github.io/W/) explains that the lite version doesn't have built-in shapes such as cubes and spheres, nor the smooth shading function (which is quite verbose).
There's also MicroW (https://xem.github.io/microW/), even smaller.
As for my own process, as I'm totally not at ease with build scripts, I minify the code manually with terser (https://xem.github.io/terser-online/) and zip it with zopfli (https://xem.github.io/zipzop/).
The repo is now quite old so I don't remember all the little manual adjustments I may have added, though your build script seems to be already very good.
I'm not able to test it currently, but I can accept your PR in a new branch and add a link to it (+ your name) in the readme and the homepage, if that's ok for you?

[sukus21]

That would be OK with me.

Looking at #29, there are a few changes from there I would like to incorporate into this branch, so give me another couple hours to get that done :)

[sukus21]

Ok, I updated a few things:

• Zipping the files is now part of build.mjs instead of a shell script
• The ect binary is now fetched as a dev dependency, instead of being present in the source tree (thanks @Lukenickerson for doing this in Change to DOMMatrix creation for performance; build script #29)

All of this combined makes it possible to build the minified and zipped versions on Windows, MacOS and Linux.

I am ready to merge now 👍

[sukus21]

...but I can accept your PR in a new branch and add a link to it...

In order to merge into a separate branch, I need you to create a branch for me to merge into, so I can update the MR to point to that branch

[xem]

Sure, I created a branch sukus21. After the merge, I'll advertize it in the readme and homepage. Thank you!

[sukus21]

Ok, I have updated the PR to target the sukus21 branch. Ready for merge 👍