Fix build and add build/installation info

.haxerc

@@ -1,4 +1,4 @@
 {
-  "version": "4.0.5",
+  "version": "a8f2911",
   "resolveLibs": "scoped"
 }

README.md

@@ -1 +1,57 @@
-[![CI](https://img.shields.io/github/workflow/status/vshaxe/vshaxe-build/CI.svg?logo=github)](https://github.com/vshaxe/vshaxe-build/actions?query=workflow%3ACI)
+# Build Tool for vshaxe
+
+[![CI](https://img.shields.io/github/workflow/status/vshaxe/vshaxe-build/CI.svg?logo=github)](https://github.com/vshaxe/vshaxe-build/actions?query=workflow%3ACI)
+
+This is a CLI and VSCode extension build tool for Haxe projects.
+
+## Installing
+
+The VSCode extension cannot currently be installed via the VSCode extension marketplace, so it must be [built from source](#building).
+
+You can install the CLI tool using your preferred Haxe package manager:
+
+Via [haxelib](https://github.com/HaxeFoundation/haxelib/):
+
+```sh
+haxelib git vshaxe-build https://github.com/vshaxe/vshaxe-build
+# You can now run
+haxelib run vshaxe-build
+```
+
+Via [lix](https://github.com/lix-pm/lix.client):
+
+```sh
+lix install github:vshaxe/vshaxe-build
+# You can now run
+lix run vshaxe-build
+```
+
+## Building
+
+Dependencies can be installed by running:
+
+```sh
+npm install
+```
+
+To package and install the VSCode extension, you must have [VSCode](https://code.visualstudio.com) and [vsce](https://github.com/microsoft/vscode-vsce#usage) installed and available in PATH.
+
+It is then possible to package and install the extension using:
+
+```sh
+vsce package
+code --install-extension vshaxe-build-*.vsix
+```
+
+If you want to work on `vshaxe-build`, you can build the various components via:
+
+```sh
+# build all components
+npx lix run vshaxe-build -t all
+# build the cli script
+npx lix run vshaxe-build -t run-script
+# build the vscode extension
+npx lix run vshaxe-build -t extension
+# build the json schema
+npx lix run vshaxe-build -t schema
+```

haxe_libraries/hxjsonast.hxml

@@ -1,3 +1,3 @@
--D hxjsonast=1.0.1
-# @install: lix --silent download "haxelib:/hxjsonast#1.0.1" into hxjsonast/1.0.1/haxelib
--cp ${HAXE_LIBCACHE}/hxjsonast/1.0.1/haxelib/src
+# @install: lix --silent download "haxelib:/hxjsonast#1.1.0" into hxjsonast/1.1.0/haxelib
+-cp ${HAXE_LIBCACHE}/hxjsonast/1.1.0/haxelib/src
+-D hxjsonast=1.1.0

haxe_libraries/hxnodejs.hxml

@@ -1,6 +1,7 @@
--D hxnodejs=10.0.0
-# @install: lix --silent download "haxelib:/hxnodejs#10.0.0" into hxnodejs/10.0.0/haxelib
--cp ${HAXE_LIBCACHE}/hxnodejs/10.0.0/haxelib/src
---macro allowPackage('sys')
-# should behave like other target defines and not be defined in macro context
---macro define('nodejs')
+# @install: lix --silent download "haxelib:/hxnodejs#12.1.0" into hxnodejs/12.1.0/haxelib
+-cp ${HAXE_LIBCACHE}/hxnodejs/12.1.0/haxelib/src
+-D hxnodejs=12.1.0
+--macro allowPackage('sys')
+# should behave like other target defines and not be defined in macro context
+--macro define('nodejs')
+--macro _internal.SuppressDeprecated.run()

haxe_libraries/json2object.hxml

@@ -1,4 +1,4 @@
--D json2object=3.6.3
-# @install: lix --silent download "haxelib:/json2object#3.6.3" into json2object/3.6.3/haxelib
+# @install: lix --silent download "haxelib:/json2object#3.10.0" into json2object/3.10.0/haxelib
 -lib hxjsonast
--cp ${HAXE_LIBCACHE}/json2object/3.6.3/haxelib/src
+-cp ${HAXE_LIBCACHE}/json2object/3.10.0/haxelib/src
+-D json2object=3.10.0

haxe_libraries/vshaxe-build.hxml

@@ -1,2 +1,3 @@
 -D vshaxe-build=0.0.1
+# @run: haxelib run-dir vshaxe-build .
 -cp .