knot-artifacts: move the artifacts binding out of the worker · Pull Request #15 · oppi.li/naut

the worker crate binds each cloudflare api with typed wasm-bindgen extern blocks in worker-sys (R2Bucket, D1Database and so on), so its calls compile to plain obj.method(...) js glue. 0.8.7 has no artifacts binding, so this crate looks the methods up at runtime instead.

it uses Reflect rather than Function.apply because of what the earlier live-fixes commit (f47f181) found. the artifacts binding hands back workers rpc stubs, where looking up any property, even .apply, is treated as a remote method. its results are thenables rather than real promises, so dyn_into::<Promise> failed; Promise.resolve wraps them instead.

typed bindings in the worker-sys style should also work: wasm-bindgen calls methods directly and doesn't check return types, and JsFuture only needs .then. i haven't tried that against live artifacts, though. if you'd like it, i'll push it as a new version of this pull after checking it on the live knot.