Closed adunne09 closed 1 month ago
As discussed in Discord, I believe this should be a JSR package. But maybe something changed in Deno 2.
Hm, maybe Deno 2 isn't picking up the rc
release? I'll take a look.
@adunne09 did you find any more details? And is this related to the WASI issue you posted in discord?
@adunne09 did you find any more details? And is this related to the WASI issue you posted in discord?
My overall goal right now is to determine the feasibility of Deno 2 as the JS runtime for a plugin-centric application. I have not found any more details other than this issue is still persisting. With this issue specifically, I'm simply confused how there is this package on jsr- https://jsr.io/@extism/extism but when I run deno add jsr:@extism/extism
, it fails.
Confirmed: deno 2 isn't picking up rc releases. You can work around this for now using deno add jsr:@extism/extism@2.0.0-rc9
. (We'll cut a v2 release of the js-sdk soon.)
Closing in favor of https://github.com/extism/js-sdk/issues/96 as it's now just a documentation issue.
https://jsr.io/@extism/extism and
import createPlugin from "jsr:@extism/extism";
here in the README indicate that there is an extism jsr package, but when I rundeno add jsr:@extism/extism
, I get:Is this the intended behavior, or is there meant to be an extism jsr package?