Post

One of the things I'm going to miss most from @deno.land is their Jupyter kernel. I use it all the time for exploring TypeScript libraries, automations, etc. I found myself wondering what Claude would do if I pointed it at this problem. The result is cdp-kernel: github.com/tlockney/cdp....

github.comGitHub - tlockney/cdp-kernel: Deno's Jupyter kernel, extracted to run notebooks on any V8 runtime over the Chrome DevTools ProtocolDeno's Jupyter kernel, extracted to run notebooks on any V8 runtime over the Chrome DevTools Protocol - tlockney/cdp-kernel

14/10/26, 10:24 pm0 reposts5 likes

The Projekt

@wearetheprojekt.bsky.social

Pulling the kernel out over CDP is a neat trick. Top level await and rich display output are what made the Deno one pleasant, so those two would show fastest whether the port holds up.

Thomas Lockney

@tlockney.net

I can't take credit for the CDP choice (nor can Claude). The Deno team actually made that change a while ago. The PR is linked in the readme.

The Projekt

@wearetheprojekt.bsky.social

Fair, the Deno team gets the credit then. The port inheriting that choice is the lucky part, since CDP gives you breakpoints and heap snapshots in the kernel for free.