Skip to content

MIDI.js dependency resolution fails - repository not found #6

@theslyprofessor

Description

@theslyprofessor

I'm encountering a dependency resolution issue when trying to install react-abc@^0.4.0 in a React project. The installation fails because it's trying to fetch from a repository that no longer exists.

Error Message:

error Command failed.
Exit code: 128
Command: git
Arguments: ls-remote --tags --heads https://github.com/paulrosen/MIDI.js.git
Directory: /path/to/project
Output:
remote: Repository not found.
fatal: repository 'https://github.com/paulrosen/MIDI.js.git/' not found

Environment:

  • Node.js
  • Yarn: 1.22.22 and Bun
  • react-abc: ^0.4.0
  • React: ^18.2.0

Steps to Reproduce:

  1. Create a new React project
  2. Add react-abc@^0.4.0 to dependencies
  3. Run yarn install
  4. Installation fails with the above error

Expected Behavior:
The package should install successfully and MIDI.js dependencies should resolve correctly.

Current Behavior:
Installation fails because the MIDI.js dependency points to https://github.com/paulrosen/MIDI.js.git which returns a 404/repository not found error.

Investigation:
It appears that the MIDI.js repository has been moved or the original paulrosen/MIDI.js repository is no longer available. I found that MIDI.js may now be available at https://github.com/mudcube/midi.js but react-abc's dependency resolution is still pointing to the old location.

Possible Solutions:

  1. Update the MIDI.js dependency to point to the correct repository
  2. Pin to a specific version of MIDI.js that's available on npm
  3. Consider using an alternative MIDI library if MIDI.js is no longer maintained

Additional Context:
This issue affects the ability to use react-abc in new projects and prevents existing projects from doing fresh installs. Any guidance on a workaround or timeline for a fix would be greatly appreciated.

Workaround Attempted:
I tried adding a resolution in package.json:

"resolutions": {
  "midi": "git+https://github.com/mudcube/midi.js.git"
}

But this leads to module resolution errors during compilation, suggesting the package structure may have changed.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions