Replies: 1 comment 1 reply
-
|
They there!
I don't think you are! Even if you were, nobody can tell you where to spend your time, so hack away! 💪
I think it's probably best that you vendor it, or, if you are going to dynamically download it, pin it to a specific release to avoid surprises. I'd go the vendor route, to make sure your package is functional once installed, even when GH is down or whatever. If / when you are ready to share it, we have a page with 3rd party packages here: https://quickjs-ng.github.io/quickjs/projects feel free to make a PR adding your project! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi! I'm brand new to Wasm, Wasmtime, and QuickJS-NG. I wrote a Python wrapper around qjs-wasi-reactor.wasm.
Am I stepping on anyone's toes? Is there any reason I shouldn't be pursuing this?
It looks like go-quickjs-wasi-reactor and js-quickjs-wasi-reactor have qjs-wasi-reactor.wasm checked back into their own source trees, and presumably included in their packages as data. I can do that too, or I can have my package download the .wasm from GitHub as part of its installation (or first use), or I could potentially create a
qjs-wasi-reactorPython package that only contains that one file (so mywasmjscode package would depend on both thewasmtimeandqjs-wasi-reactorpackages). Does anyone have any thoughts about this?Thanks!
Beta Was this translation helpful? Give feedback.
All reactions