How about using `async` functions?

What do you think about using async functions to prevent callback hells?

webdx7/dist/dx7/dx7-awn.js

Lines 15 to 25 in d056aa3

	static importScripts (actx) {
	var origin = location.origin + "/";
	return new Promise( (resolve) => {
	actx.audioWorklet.addModule(origin + "dx7/wasm/dx7.wasm.js").then(() => {
	actx.audioWorklet.addModule(origin + "dx7/wasm/dx7.js").then(() => {
	actx.audioWorklet.addModule(origin + "../wamsdk/wam-processor.js").then(() => {
	actx.audioWorklet.addModule(origin + "dx7/dx7-awp.js").then(() => {
	resolve();
	}) }) }) });
	})
	}

static async importScripts(actx)
{
	const origin = location.origin + '/';
	await actx.audioWorklet.addModule(origin + "dx7/wasm/dx7.wasm.js");
	await actx.audioWorklet.addModule(origin + "dx7/wasm/dx7.js");
	await actx.audioWorklet.addModule(origin + "../wamsdk/wam-processor.js");
	await actx.audioWorklet.addModule(origin + "dx7/dx7-awp.js");
}

[jariseon]

yeah async/await makes it much more cleaner, and looks like all major browser support it. thanks, i will clean this up in next update. WASM code transfer to processor side will also be greatly simplified once constructor (options) becomes available.