It works on your notebook, but on [mine](https://obs.run/@fil/testing-deno-obs-run) I get this error that I don't know how to tackle: > error: Uncaught (in promise) RuntimeError: document is not defined

Thanks for giving it a try! There are a variety of tweaks that are needed to run "node" packages in a deno environment. The ObservableHQ runtime needed one fix that I am working around WRT the global "setImmediate" function available in Node: https://github.com/observablehq/runtime/pull/331 Deno has a node compatibility mode that you could try in the short term which enables more "node" things in the runtime for things to reference. You can also try setting them yourself in the first line of your notebook. I can take a look later at your example and see what else may need to be "polly-filled" for what you end-up running in the notebook. But in general you should only be trying to run "Deno" code in your notebook rather than any existing node content. The main thing I need to test is all the ObservableHQ runtime functionality to find if there are additional concern cases of references that are node-specific other than the one I identified so far. Here is a http server example running from a notebook, I have it deployed to heroku using the --watch variant and when I publish a new version of the notebook it automatically updates on heroku without any additional input: https://observablehq.com/@keystroke/keystroke-cloud