dOrgJelli
dOrgJelli
@krisbitney can you create a more detailed devexp description in this issue?
For reference, see this mini-hack where wrappers are being hosted at an HTTP endpoint: https://github.com/polywrap/mini-hacks/issues/23
@krisbitney when building using the `vm` strategy, it uses a pre-built docker image as the "vm" and runs a build script within it. This means that, in order for build...
Great point, agreed! The URI resolution path should not change just because it was found in cache.
Agreed, we can create a new folder within integrations called `framework` that can include tailored framework integrations. Some others that would be cool to see here: - Unity - React-Native...
Sounds like a great plan @cbrzn, I'm all for it!
@cbrzn what requirements would we need to meet for this task to be completed? Some thoughts: - All wasm tests are runnable in the new repo - Feature matrix can...
IMO all user-facing functions (on the client) should support both, but everything underneath should use URI.
Here's a quick brainstorm from @Niraj-Kamdar https://hackmd.io/uuqcNzpCTwKDrbwSNp1sJg