Skip to content
This repository has been archived by the owner on Aug 1, 2023. It is now read-only.

npm install broken #502

Open
rchrdw opened this issue Sep 20, 2022 · 1 comment
Open

npm install broken #502

rchrdw opened this issue Sep 20, 2022 · 1 comment
Labels
need/triage Needs initial labeling and prioritization

Comments

@rchrdw
Copy link

rchrdw commented Sep 20, 2022

This is currently broken and cannot be installed

❯ npm i ipfs-interop
npm ERR! code 1
npm ERR! The git reference could not be found
npm ERR! command git --no-replace-objects checkout feat/upgrade-to-esm-libp2p
npm ERR! error: pathspec 'feat/upgrade-to-esm-libp2p' did not match any file(s) known to git

@rchrdw rchrdw added the need/triage Needs initial labeling and prioritization label Sep 20, 2022
@welcome
Copy link

welcome bot commented Sep 20, 2022

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:

  • "Priority" labels will show how urgent this is for the team.
  • "Status" labels will show if this is ready to be worked on, blocked, or in progress.
  • "Need" labels will indicate if additional input or analysis is required.

Finally, remember to use https://discuss.ipfs.io if you just need general support.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
need/triage Needs initial labeling and prioritization
Projects
None yet
Development

No branches or pull requests

1 participant