j11s Posts - Deno

j11s

•Created by j11s on 12/2/2024 in #help

comparable functionality to node:repl in deno?

According to https://docs.deno.com/api/node/repl/ this Node API is currently not implemented in Deno (yet?). Is there anything comparable today? In particular, I'm interested in building my own custom REPLServer -- with a custom eval and custom completer. Is there a plan to support this Node API in the future?

2 replies

DDeno

•Created by j11s on 5/11/2023 in #help

Deno debugging failure: Argument 0 must be a buffer source

I have TWO Deno project with and cannot use the debugger with ONE of them. One project debugs fine, the other does not. I do not know where to start to mitigate the problem. I see this problem with VS Code fronting the debugger and by using chrome://inspect directly. First, the error message:

/home/xxx/.local/bin/deno run --inspect-brk --allow-all src/xxx-api-server.ts
Uncaught TypeError TypeError: WebAssembly.compile(): Argument 0 must be a buffer source
    at eventLoopTick (core/01_core.js:181:11)
01_core.js:181
Debugger listening on ws://127.0.0.1:9229/ws/e8d67075-6dae-493c-83d5-73d26738d2b9
Visit chrome://inspect to connect to the debugger.
Deno is waiting for debugger to connect.
Debugger session started.
error: Uncaught (in promise) TypeError: WebAssembly.compile(): Argument 0 must be a buffer source
    at eventLoopTick (ext:core/01_core.js:181:11)
Process exited with code 1

/home/xxx/.local/bin/deno run --inspect-brk --allow-all src/xxx-api-server.ts
Uncaught TypeError TypeError: WebAssembly.compile(): Argument 0 must be a buffer source
    at eventLoopTick (core/01_core.js:181:11)
01_core.js:181
Debugger listening on ws://127.0.0.1:9229/ws/e8d67075-6dae-493c-83d5-73d26738d2b9
Visit chrome://inspect to connect to the debugger.
Deno is waiting for debugger to connect.
Debugger session started.
error: Uncaught (in promise) TypeError: WebAssembly.compile(): Argument 0 must be a buffer source
    at eventLoopTick (ext:core/01_core.js:181:11)
Process exited with code 1

System details: Deno 1.33.2 (have tried 1.33.1, too) VS Code 1.78.1 (and the previous version, as well) Plugin: Deno Plugin latest OS: both Linux and Windows The upshot is that there is something about this specific project that is causing a bug with the debugger. I don't know to whom I should report the problem (Deno or Google/Chrome). I'd be satisfied with a workaround to be able to debug it again, but I do not know where to start. Much thanks.

5 replies