Support webassembly instantiate streaming

[Tucker-Eric]

This allows passing a Response or Promise<Response> to loadPolicy which will pass the response to WebAssembly.instantiateStreaming() instead of WebAssembly.instantiate() to allow fulfilling the suggestion from MDN

[srenatus]

Very nice, I've been wanting that, too. ✨ Thanks!

[Tucker-Eric]

@srenatus thank you! What're the chances we could get a version bump with these changes and #424 in it?

[srenatus]

I'll take care of it next week!

[srenatus]

✔️ It's released: 1.9.0.

I'm curious, what's your use case? How are you using OPA's wasm modules? 😃

[Tucker-Eric]

Thank you! @srenatus

We're using it in a monorepo. The policies/wasm build is all in its own package that's imported into the apps using it. The service itself needed to be usable in browsers and Node runtime so we're bundling the wasm policy with vite.

That same service is used by:

• Frontend applications to support dynamic views based RBAC/ABAC
• Node api
• Python api (fetches wasm stream and loads it into opa-wasm)

So we get to define the policies in a central place and essentially have 3 different runtimes benefit from using the exact same policies without having to redefine and keep everything in sync for each platform.

[srenatus]

That's awesome. 🚀

I'm currently working on something related to

Frontend applications to support dynamic views based RBAC/ABAC

too, so I've been wondering if you'd like to share notes. Are you on the OPA Slack?

[Tucker-Eric]

@srenatus I'd love to share notes and approaches! I'm not in the OPA Slack, do I need an invite to join?

[srenatus]

https://slack.openpolicyagent.org/