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
We recently switched to kubo-rpc-client as a drop-in replacement for ipfs-http-client in our project. However, we're encountering some TypeScript build errors after making this change.
The errors appear to be related to resolving the ReadableStream type, as illustrated in the following screenshot:
For reference, we are currently using TypeScript version 5.1.6 and @types/node version 20.5.1.
We have observed that ReadableStream is declared under module 'stream/web' in @types/node, but it seems like TypeScript is having trouble resolving this type.
We have already attempted the following troubleshooting steps:
Ensured the latest versions of TypeScript and @types/node are installed.
Checked the tsconfig.json to make sure it does not limit TypeScript's type resolution in any way.
However, these steps did not resolve the issue. We're seeking assistance to understand why these build errors are occurring and how we can fix them. Any suggestions or insights would be much appreciated.
The text was updated successfully, but these errors were encountered:
We recently switched to kubo-rpc-client as a drop-in replacement for ipfs-http-client in our project. However, we're encountering some TypeScript build errors after making this change.
The errors appear to be related to resolving the ReadableStream type, as illustrated in the following screenshot:
For reference, we are currently using TypeScript version 5.1.6 and @types/node version 20.5.1.
We have observed that ReadableStream is declared under module 'stream/web' in @types/node, but it seems like TypeScript is having trouble resolving this type.
We have already attempted the following troubleshooting steps:
However, these steps did not resolve the issue. We're seeking assistance to understand why these build errors are occurring and how we can fix them. Any suggestions or insights would be much appreciated.
The text was updated successfully, but these errors were encountered: