You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is my preferred way to use it with Deno. I am wondering if it could be considered the standard way of using @msgpack/msgpack from Deno. If so, perhaps this could be given an example with just deno.js and the other ones could have longer names. Also the only thing that changes in the other examples is the URL. Perhaps it could just be comments in deno.js:
#!/usr/bin/env deno run
/* eslint-disable no-console */import*asmsgpackfrom'npm:@msgpack/msgpack';// from UNPKG//import * as msgpack from "https://unpkg.com/@msgpack/msgpack/mod.ts";// from esm.sh//import * as msgpack from "https://esm.sh/@msgpack/msgpack/mod.ts";// from jsDelivr//import * as msgpack from "https://cdn.jsdelivr.net/npm/@msgpack/msgpack/mod.ts";console.log(msgpack.decode(msgpack.encode("Hello, world!")));
The text was updated successfully, but these errors were encountered:
gfx
added a commit
that referenced
this issue
Aug 8, 2023
This works for me in Deno:
This is my preferred way to use it with Deno. I am wondering if it could be considered the standard way of using
@msgpack/msgpack
from Deno. If so, perhaps this could be given an example with justdeno.js
and the other ones could have longer names. Also the only thing that changes in the other examples is the URL. Perhaps it could just be comments indeno.js
:The text was updated successfully, but these errors were encountered: