Set up GitHub Actions CI for JavaScript

[GreyCat]

No description provided.

[generalmimon]

If the kaitai_compress is meant to be a library that users will integrate into their applications, the general consensus is that package-lock.json shouldn't be tracked by Git. See

• https://jbeckwith.com/2019/12/18/package-lock/
• https://www.twilio.com/blog/lockfiles-nodejs

Actually we should also eliminate yarn.lock in https://github.com/kaitai-io/kaitai_struct_loader.

[generalmimon]

I'd say it's better to just specify the -t parameter multiple times on a single ksc invocation than launch a separate instance of ksc for each target, which is unnecessary (and it would also print everything multiple times). Like this:

ksc --verbose all -t javascript -t python -t ruby -d compiled ksy/*.ksy

KSC also adds the compiled/{javascript,python,ruby}/ subdirectories automatically, so you don't need to take care of that anymore.

---

I'm also not a fan of --verbose all - this usually fills pages and pages of logs with confused and too detailed stream of unnecessary debug information. My favorite verbosity is --verbose file, that is usually enough.

[GreyCat]

Makes sense, I totally forgot about multiple -t, let me fix this!

[generalmimon]

Looks good to me. You could also add package-lock.json to .gitignore given that we agreed that it doesn't make sense to track it with Git, but that can be done independently of this PR.

[generalmimon]

My personal preference would be to always use space as a parameter name/value separator, as ksc --help suggests:

$ ksc --help
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding="UTF-8"
kaitai-struct-compiler 0.10-SNAPSHOT
Usage: kaitai-struct-compiler [options] <file>...

  <file>...                source files (.ksy)
  -t, --target <language>  target languages (graphviz, csharp, rust, all, perl, java, go, cpp_stl, php, lua, python, nim, html, ruby, construct, javascript)
  -d, --outdir <directory>
                           output directory (filenames will be auto-generated)
  (...)
  --verbose <value>        verbose output

Note that it's written as --verbose <value>, not --verbose=<value>.

Suggested change

	ksc \
	--verbose=file \
	-t javascript \
	-t python\
	-t ruby \
	--outdir=compiled \
	ksy/*.ksy
	ksc \
	--verbose file \
	-t javascript \
	-t python\
	-t ruby \
	--outdir compiled \
	ksy/*.ksy

Sorry for nitpicking.