Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bug: broken @libp2p/interface-compliance-tests #1974

Closed
danisharora099 opened this issue Aug 16, 2023 · 0 comments · Fixed by #1983 or waku-org/js-waku#1525
Closed

bug: broken @libp2p/interface-compliance-tests #1974

danisharora099 opened this issue Aug 16, 2023 · 0 comments · Fixed by #1983 or waku-org/js-waku#1525
Assignees
Labels
need/triage Needs initial labeling and prioritization

Comments

@danisharora099
Copy link

  • Version: 0.46.3

  • Platform: macos

  • Subsystem: compliance tests

Severity: high

Description:

on the upgrade of @libp2p/interface-peer-discovery-compliance-tests to @libp2p/[email protected] the package breaks because aegir is installed as a dev dependency on the latter while it's needed to run tests which was installed as a dependency on the former package.

the solution can be simply moving aegir to dependency or to install chai as a dependency and using that instead of aegir/chai?

@danisharora099 danisharora099 added the need/triage Needs initial labeling and prioritization label Aug 16, 2023
maschad added a commit to maschad/js-libp2p that referenced this issue Aug 20, 2023
achingbrain added a commit that referenced this issue Aug 24, 2023
The interface compliance tests depend on aegir to run the tests so
make it a dep instead of a dev dep.

Fixes #1974
achingbrain pushed a commit that referenced this issue Aug 24, 2023
Given that this package is primarily responsible for testing, I think that `aegir` is required as a dependency to utilize it properly.

Closes #1974
This was referenced Jan 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment