Method Transport#filter() doesn't matches unix sockets

[rumkin]

According to the source code, TCP transport method Transport#filter() relies on mafmt's TCP matcher function (mafmt /src/index.js:18) which doesn't match unix sockets: src/index.js:135. So it's impossible to listen unix sockets. And attempts to provide unix path to Transport fails:

import path from 'path'

import Libp2p from 'libp2p'
import Tcp from 'libp2p-tcp'
import Mplex from 'libp2p-mplex'
import PeerId from 'peer-id'
import PeerInfo from 'peer-info'
import Plaintext from 'libp2p/src/insecure/plaintext.js'



const serverPeer = await PeerId.create()
const serverInfo = new PeerInfo(serverPeer)

serverInfo.multiaddrs.add(
  path.join('/unix', path.resolve('unix.sock'))
)

const node = await Libp2p.create({
    peerInfo: serverInfo,
    modules: {
      transport: [Tcp],
      connEncryption: [Plaintext],
      streamMuxer: [Mplex],
    },
})

The code throws ERR_NO_VALID_ADDRESSES. I'm not sure if it the TCP or mafmt package error. I'm not sure if it the TCP or mafmt package error, but while it's hard to understand which protocol is unix port listening I think it relates to this package.

[jacobheun]

Filter needs to be updated here to check for tcp and unix multiaddrs. Unix could be added to the mafmt module, but that's probably unnecessary right now since we only support a single structure to the address (/unix/<path>).

[github-actions]

🎉 This issue has been resolved in version 6.0.2 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀