Closed 10dimensions closed 1 year ago
Thank you for submitting your first issue to this repository! A maintainer will be here shortly to triage and review. In the meantime, please double-check that you have provided all the necessary information to make this process easy! Any information that can help save additional round trips is useful! We currently aim to give initial feedback within two business days. If this does not happen, feel free to leave a comment. Please keep an eye on how this issue will be labeled, as labels give an overview of priorities, assignments and additional actions requested by the maintainers:
Finally, remember to use https://discuss.ipfs.io if you just need general support.
@10dimensions : can you please provide a reproducible repo? In case it helps, please be aware of some recent breaking changes that were made: https://github.com/ipfs/js-ipfs/blob/master/docs/upgrading/v0.62-v0.63.md
i'm getting similar issue while using it with cloud functions. i've created an issue with reproducible demo https://github.com/ipfs/js-ipfs/issues/4180
Module not found: Package path . is not exported from package
means you are trying to require
an ESM module.
Your source code is in ESM but chances are your output settings are producing CJS - please check the output folder for the type of JS being emitted and update your config to emit ESM instead.
@achingbrain i'm having the same problem trying to create a github action that uses this package. i use vercel/ncc to build and i have no idea what this package is missing in order to be used.
Module not found: Package path . is not exported from package C:\projects\amberfi\dapp\my-dapp\node_modules\ipfs-http-client (see exports field in C:\projects\amberfi\dapp\my-dapp\node_modules\ipfs-http-client\package.json) 8 | }); 9 | };
Version: 57.0.1
Platform: Google Chrome
Subsystem: Imported in a Next.js component
Severity:
Critical - System crash, application panic.
Description:
Imported ipfs-http-client module. Which is referenced by an internal npm package. Finally, import inside a Next.js UI component
Steps to reproduce the error: