### JSON file structure for wasm/asm module
- `name` — name with which the module will be built
- `res_folder` — path, relative to the .json file, to the folder where the module will be built
- `wasm` — whether to build wasm module (*.js and *.wasm)
- `asm` — whether to build asm module (*_ie.js and *.js.mem)
- `run_before` — path, relative to the .json file, to .py file that needs to be executed before building the module. Or python in-line code.
- `run_after` — path, relative to the .json file, to .py file that needs to be executed after building the module. Or python in-line code.
- `base_js_content` — path, relative to the .json file, to .js file containing //module which will be replaced with the built module
- `compiler_flags` — array of compilation flags and options
- `exported_functions` — array of function names that will be called from the module
- `include_path` — array of paths, relative to the .json file, for include directories
- `define` — array of defines
- `compile_files_array` — array of objects containing:
    - `name` — unique name, relative to other names in compile_files_array array
	- `folder` — path, relative to the .json file, to folder with included files
	- `files` — array of included file names, located in folder (hierarchy ../ and ./*/ allowed)
	- `include_path` — optional array of paths, relative to the .json file, for include directories
	- `define` — optional array of defines
- `sources` — optional array of paths, relative to the .json file, to files that don't require precompilation. For example, .a or .o files.