Deno interoperability with npm has come a long way. We'd like to use the Deno runtime without any deno-specific dependencies. If we could use the postgres npm module instead, this would allow us to manage dependencies in package.json instead of deno.json, get rid of the buggy Deno tooling for VSCode, and create code that works on both Node and Deno.
Unfortunately, when I try postgres@3.4.3 with Deno, I get a connection timeout, while the same code works with the deno port.
Error: write CONNECT_TIMEOUT undefined:undefined
at connectTimedOut (file://my-project/node_modules/.deno/postgres@3.4.3/node_modules/postgres/src/connection.js:257:20)
at Timeout.done [as _onTimeout] (file://my-project/node_modules/.deno/postgres@3.4.3/node_modules/postgres/src/connection.js:1035:8)
at cb (ext:deno_node/internal/timers.mjs:63:31)
at Object.action (ext:deno_web/02_timers.js:151:11)
at handleTimerMacrotask (ext:deno_web/02_timers.js:65:10)
at eventLoopTick (ext:core/01_core.js:189:21)
at cachedError (file://my-project/node_modules/.deno/postgres@3.4.3/node_modules/postgres/src/query.js:170:23)
at new Query (file://my-project/node_modules/.deno/postgres@3.4.3/node_modules/postgres/src/query.js:36:24)
at sql (file://my-project/node_modules/.deno/postgres@3.4.3/node_modules/postgres/src/index.js:112:11)
Deno interoperability with npm has come a long way. We'd like to use the Deno runtime without any deno-specific dependencies. If we could use the
postgres
npm module instead, this would allow us to manage dependencies inpackage.json
instead ofdeno.json
, get rid of the buggy Deno tooling for VSCode, and create code that works on both Node and Deno.Unfortunately, when I try
postgres@3.4.3
with Deno, I get a connection timeout, while the same code works with the deno port.Any chance to get this resolved?