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
The README claims that js-libp2p can be run using: npm run test -- -t node.
That doesn't work:
npm ERR! Lifecycle script `test` failed with error:
npm ERR! Error: Missing script: "test"
To see a list of scripts, run:
npm run
npm ERR! in workspace: [email protected]
npm ERR! at location: /Users/marten/src/go/src/github.com/libp2p/js-libp2p/interop
npm ERR! Missing script: test
npm ERR! A complete log of this run can be found in: /Users/marten/.npm/_logs/2023-08-28T05_04_05_748Z-debug-0.log
Looking at the ENTRYPOINT of the Dockerfile, this should probably be test:interop:multidim, but I'm not sure which command line flags would be needed.
The text was updated successfully, but these errors were encountered:
I'm going to close this issue in favor of #282 because they are the same issue. npm run test -- -t node is meant to be run within the js test-plans implementation.
The README claims that js-libp2p can be run using:
npm run test -- -t node
.That doesn't work:
Looking at the ENTRYPOINT of the Dockerfile, this should probably be
test:interop:multidim
, but I'm not sure which command line flags would be needed.The text was updated successfully, but these errors were encountered: