Repository navigation
Use node's fetch instead of cross-fetch #23
Description
As following warning message, node-domexception is deprecated, it is a nested dependency of node-fetch (node-fetch also is a dependency of cross-fetch). Since node original support fetch since v18, can we remove cross-fetch/node-fetch polyfill, use node's original fetch instead?
npm warn deprecated node-domexception@1.0.0: Use your platform's native DOMException instead @libsql/client 0.15.9
└─┬ @libsql/hrana-client 0.7.0
└─┬ node-fetch 3.3.2
├─┬ fetch-blob 3.2.0
│ └── node-domexception 1.0.0
└─┬ formdata-polyfill 4.0.10
└─┬ fetch-blob 3.2.0
└── node-domexception 1.0.0
Activity
jrmajor commentedon Aug 10, 2025
node-fetchalso requiresweb-streams-polyfill, which is a very large package (8.62 MB).jpc-ae commentedon Dec 5, 2025
+1 to this. Will a pull request help, or is this part of the client no longer being maintained?
kenn commentedon Feb 16, 2026
+1 to remove loud
punycodewarning.The root cause is the same
cross-fetchtr46@0.0.3(from 2016) doesrequire("punycode")which triggers the Node.js deprecation warning. It's the Turso/LibSQL database client that ultimately pulls it in.MMMikeM commentedon Mar 27, 2026
@honzasp @penberg is this something you're open to? Anything I could do to assist?
honzasp commentedon Mar 28, 2026
Hello, I haven't been working on this for more than 2 years, but @penberg might be able to assist you :)
MMMikeM commentedon Mar 28, 2026
Sorry for the tag Jan, I decided them based on highest contributions 😅
Remove cross-fetch dependency, use native fetch globals
adutton commentedon Apr 15, 2026
I created a PR #27 to remove the cross-fetch dependency.