fixing this issue with multiaddr (WIP)

This commit is contained in:
Pavel Murygin 2022-08-30 16:07:08 +03:00
parent d9db05fbd1
commit 924ea45509
3 changed files with 5 additions and 3 deletions

View File

@ -26,6 +26,8 @@ import type { MultiaddrInput } from '@multiformats/multiaddr';
import { Multiaddr } from '@multiformats/multiaddr';
import { Connection } from '@libp2p/interface-connection';
export { Multiaddr } from '@multiformats/multiaddr';
export const PROTOCOL_NAME = '/fluence/particle/2.0.0';
/**

View File

@ -1,4 +1,4 @@
import { Multiaddr } from '@multiformats/multiaddr';
import { Multiaddr } from '@fluencelabs/connection';
import { nodes } from '../connection';
import { FluencePeer } from '../../index';

View File

@ -13,7 +13,7 @@
* See the License for the specific language governing permissions and
* limitations under the License.
*/
import { RelayConnection } from '@fluencelabs/connection';
import { RelayConnection, Multiaddr } from '@fluencelabs/connection';
import { FluenceConnection } from '@fluencelabs/interfaces';
import { KeyPair } from '@fluencelabs/keypair';
import { FluenceAppService, loadDefaults, loadWasmFromFileSystem, loadWasmFromServer } from '@fluencelabs/marine-js';
@ -576,7 +576,7 @@ export class FluencePeer {
() => {
item.onStageChange({ stage: 'sent' });
},
(e) => {
(e: any) => {
log.error(e);
},
);