Guy Bedford

ComponentizeJS doesn't support debug builds at all - this is due to the nature of the splicing code in https://github.com/bytecodealliance/ComponentizeJS/blob/main/crates/spidermonkey-embedding-splicer/src/splice.rs. Supporting debug builds would be a very worthwhile feature, but...

Thanks for bringing this up, your workaround is roughly the right sort of approach. Posted an upstream issue in https://github.com/bytecodealliance/StarlingMonkey/issues/192. In the meantime we could inline an approach similar to...

Check that you're definitely using the latest ComponentizeJS in your node_modules folder verifying the version.

Are you trying to use `performance.now()` in the JS initialization outside of a component exported function? Wizer-time use of the `performance` global is not permitted.

i.e. compile time is not the time to do timing stuff.

You're writing something like this: ```js // this is a wizer time use of the performance global - NOT ALLOWED const start = performance.now(); export const run = { run...

So looking at your JS code, `enable()` accesses `performance.timeOrigin` and `enable()` is called at Wizer time during the initialization of the application. The bug here is that we don't throw...

Great to hear, we should definitely improve the error though.

A JS-based shim could well be a starting point, although in terms of that being a development blocker often a simple build step can also be used to build in...

Thanks for taking a look and I believe you're right on the implementation aspects. The alternative would be to just use `object` and then to define the validations in line,...