Refactor wasm_wrappers: rename some folders; move code to different files; tests now use TypeScript

Author: ImplOfAnImpl

.dockerignore

@@ -45,6 +45,8 @@ test/config.ini
 
 # wasm
 wasm-wrappers/pkg/
+wasm-wrappers/js-bindings-test/test.js
+wasm-wrappers/js-bindings-test/test.js.map
 
 # 'mintlayer-data' will be mapped to home directories of docker containers, so everything
 # inside it will be generated by the containers.

.github/workflows/wasm.yml

@@ -35,14 +35,19 @@ jobs:
         uses: actions/setup-node@v3
         with:
           node-version: ${{ matrix.node-version }}
+      - name: Install TypeScript
+        run: npm install typescript
       - name: Install wasm-pack
         run: cargo install wasm-pack
       - name: Build the wasm module
         working-directory: ./wasm-wrappers
         run: wasm-pack build --target nodejs
+      - name: Compile the tests
+        working-directory: ./wasm-wrappers
+        run: tsc --project js-bindings-test/tsconfig.json
       - name: Run the tests
         working-directory: ./wasm-wrappers
-        run: node js-bindings/node-entry.js
+        run: node --enable-source-maps js-bindings-test/node-entry.js
 
   wasm_artifacts:
     runs-on: ubuntu-latest

.gitignore

@@ -43,6 +43,8 @@ test/config.ini
 
 # wasm
 wasm-wrappers/pkg/
+wasm-wrappers/js-bindings-test/test.js
+wasm-wrappers/js-bindings-test/test.js.map
 
 # 'mintlayer-data' will be mapped to home directories of docker containers, so everything
 # inside it will be generated by the containers.

build-tools/codecheck/codecheck.py

@@ -325,6 +325,7 @@ def check_files_end_with_newline():
     # list of files exempted from checks
     exempted_files = [
         'wasm-wrappers/doc/*',
+        'wasm-wrappers/js-bindings-test/test.js',
     ]
 
     ok = True

wasm-wrappers/README.md

@@ -1,11 +1,12 @@
-## Basic wasm bindings for mintlayer
+# Basic wasm bindings for mintlayer
 
 This module has different basic functionalities of mintlayer compiled into wasm for various purposes, primarily interfacing with other systems and languages without having to rewrite code.
 
 ##### Note: This was tested on x86_64 Linux, and may not work on other platforms. It didn't work on M1 Mac directly (particularly the build. A pre-built wasm binary works fine on a browser, see below for more information).
 
+## Running the tests
 
-### To run in a web browser
+### Preparation
 
 Make sure you have wasm-pack and the wasm32-unknown-unknown target installed:
 
@@ -16,48 +17,53 @@ cargo install wasm-pack
 
 Also make sure you have `clang` installed. It's required.
 
-To build the wasm package from the crate, run (in the wasm Cargo.toml directory):
-
-```
-wasm-pack build --target web
-```
-
 **Note for mac users**: `llvm` installed by Xcode doesn't support wasm targets, but the homebrew version does, these commands may make it possible to compile to wasm targets. Note that using these commands could have other side effects on your toolchain. Please consider researching the clang toolchain and how it works before using them. We do not recommend copying and pasting commands without fully understanding the side-effects.
 ```
 brew install llvm
 AR=/opt/homebrew/opt/llvm/bin/llvm-ar CC=/opt/homebrew/opt/llvm/bin/clang wasm-pack build --target web
 ```
 
-To test the wasm binary. First, install `http-server` web server (feel free to use any other web-server of your choosing):
+Also, install TypeScript:
+```
+npm install -g typescript
+```
+
+### Compile the tests via `tsc`
 
+In the wasm Cargo.toml directory, run:
 ```
-cargo install http-server
+tsc --project js-bindings-test/tsconfig.json
 ```
 
-Then run the http server, and then choose the file `js-bindings/index.html`:
+### Running the tests in a web browser
+
+To build the wasm package from the crate, run (in the wasm Cargo.toml directory):
 
 ```
-http-server --port 8080 --verbose
+wasm-pack build --target web
 ```
 
-If you're using a remote server, either tunnel to port 8080, or expose that port and run this (assuming you understand the security risks):
+To test the wasm binary. First, install `http-server` web server (feel free to use any other web-server of your choosing):
 
 ```
-http-server --port 8080 --host 0.0.0.0 --verbose
+cargo install http-server
 ```
 
-The ported wasm functions are exported to the file `js-bindings/index.js` and used in the file `js-bindings/index.html` with a basic test/example in them using JavaScript. Use your browser's console to see the output.
+Then run the http server, and then choose the file `js-bindings-test/index.html`:
 
-### To run in Node.js
+```
+http-server --port 8080
+```
 
-Make sure you have wasm-pack and the wasm32-unknown-unknown target installed:
+If you're using a remote server, either tunnel to port 8080, or expose that port and run this (assuming you understand the security risks):
 
 ```
-rustup target add wasm32-unknown-unknown
-cargo install wasm-pack
+http-server --port 8080 --host 0.0.0.0
 ```
 
-Also make sure you have `clang` installed. It's required.
+The ported wasm functions are exported to the file `js-bindings-test/index.js` and used in the file `js-bindings-test/index.html` with a basic test/example in them using JavaScript. Use your browser's console to see the output.
+
+### Running the tests in Node.js
 
 To build the wasm package from the crate, run (in the wasm Cargo.toml directory):
 
@@ -68,7 +74,7 @@ wasm-pack build --target nodejs
 Finally, to run the example, run:
 
 ```
-node js-bindings/node-entry.js
+node --enable-source-maps  js-bindings-test/node-entry.js
 ```
 
 ### Further documentation on wasm

wasm-wrappers/js-bindings/index.html renamed to wasm-wrappers/js-bindings-test/index.html

@@ -1,4 +1,4 @@
-import { run_test } from "./wasm_test.js";
+import { run_test } from "./test.js";
 
 async function node_run() {
   await run_test();