You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$ ipfs-deploy public -p infura -d cloudflare
📂 Deploying public directory.
📦 Calculating size of public…
🚚 Directory public weighs 14.2 MiB.
⚙️ Validating pinners configurations…
⚙️ Validating DNS providers configurations…
📠 Uploading and pinning to Infura…
❌ An error has occurred:
TypeError: RequestInit: duplex option is required when sending a body.
at Object.fetch (node:internal/deps/undici/undici:14062:11)
This error happens when using Node 18.13.0+ or Node 19.1.0+ while pinning to any pin service that is implemented with the ipfs-http-client library (Infura, c4rex, dappnode).
Macil
changed the title
Broken on Node 19: "TypeError: RequestInit: duplex option is required when sending a body"
Broken in Node 18.13: "TypeError: RequestInit: duplex option is required when sending a body"
Jan 29, 2023
Fixing this issue would onboard many users to decentralised hosting from simple react or solidjs build files using a simple ipfs-deploy. Excited and looking to see when it gets tested and merged. Thanks in advanced for those that help
This error happens when using Node 18.13.0+ or Node 19.1.0+ while pinning to any pin service that is implemented with the ipfs-http-client library (Infura, c4rex, dappnode).
The root cause is ipfs/js-ipfs#4276 and nodejs/node#46221. The issue is fixed in ipfs-http-client v60.0.0.
The text was updated successfully, but these errors were encountered: