If you're curious the changes that were required, the diff can be seen here.
Mostly it was a matter of changing file paths/extensions in the
import statements, but there were actually some typing bugs that Deno caught which somehow weren't caught in the upstream repo, like this import of
ALL which doesn't exist in
request-message and had to be updated to
Hi @bradenmacdonald ,
Thanks for the work that went into that port! And thanks @chris3 for the reminder about this thread 😉
I've had a chat with the driver team and Deno has come up on their future planning wall. Would you @bradenmacdonald be up for submitting a pull request with your changes?
@abk Well it took me much longer than I'd hoped.... But I got some time over the holidays and have refreshed my Deno port to be based on the latest version 4.4, and I've opened four pull requests to contribute the changes: Proposal: A tool for generating a deno-optimized version of the driver by bradenmacdonald · Pull Req...
For those reading this and looking for a Deno version that can be used today, I have also posted it to deno.land at https://deno.land/x/neo4j_lite_client