WebAssembly.CompileError
Baseline Widely available
This feature is well established and works across many devices and browser versions. It’s been available across browsers since October 2017.
TheWebAssembly.CompileError object indicates an error during WebAssembly decoding or validation.
In this article
Constructor
WebAssembly.CompileError()Creates a new
WebAssembly.CompileErrorobject.
Instance properties
WebAssembly.CompileError.prototype.messageError message. Inherited from
Error.WebAssembly.CompileError.prototype.nameError name. Inherited from
Error.WebAssembly.CompileError.prototype.causeError cause. Inherited from
Error.WebAssembly.CompileError.prototype.fileNameNon-standardPath to file that raised this error. Inherited from
Error.WebAssembly.CompileError.prototype.lineNumberNon-standardLine number in file that raised this error. Inherited from
Error.WebAssembly.CompileError.prototype.columnNumberNon-standardColumn number in line that raised this error. Inherited from
Error.WebAssembly.CompileError.prototype.stackNon-standardStack trace. Inherited from
Error.
Instance methods
WebAssembly.CompileError.prototype.toString()Returns a string representing the specified
Errorobject. Inherited fromError.
Examples
>Creating a new CompileError instance
The following snippet creates a newCompileError instance, and logs its details to the console:
try { throw new WebAssembly.CompileError("Hello", "someFile", 10);} catch (e) { console.log(e instanceof CompileError); // true console.log(e.message); // "Hello" console.log(e.name); // "CompileError" console.log(e.fileName); // "someFile" console.log(e.lineNumber); // 10 console.log(e.columnNumber); // 0 console.log(e.stack); // returns the location where the code was run}Specifications
| Specification |
|---|
| WebAssembly JavaScript Interface> # exceptiondef-compileerror> |
| ECMAScript® 2026 Language Specification> # sec-native-error-types-used-in-this-standard> |