Renée

the new static-eval doesn't support function expressions like the `body` option in: ```js cwise({ body: () => {} }) ``` I think because of this patch https://github.com/substack/static-eval/pull/18 static-module has a...

no, i forgot about it :smile: i'll aim to work on this on Friday. a PR would be welcome as well of course. I think the way to go here...

The refactor is a bit trickier than I anticipated, and I haven't had the time to make it work yet unfortunately :(

@telamonian I think I tried a few approaches but none of them worked out so I discarded them. For now @archmoj's approach where we just add an option to opt...

#56 updates to the static-eval with @archmoj's fix but I'm not sure if it's enough. I tried using that branch in my local cwise clone and passing `{ allowAccessToMethodsOnFunctions: true...

hm, static-eval might be bailing out somewhere else as well then :/

Hmm, this works for me with 7.1.0: ```js setImmediate(function () { console.log('test') }) ``` Could you share an example snippet that reproduces the problem?

I think calling `lib/rustify` to get the same behaviour in Node might be difficult because it is asynchronous, while the ``` rust`` ``` template tag is 'synchronous' (once compiled through...

I'm not aware of any way to do this in the browser, no. There is no cross platform API for bytecode caches.

you probably need to set some content security policy header to allow evals. i don't think this package can control that in any way.