New Case Study:See how Anthropic automated 95% of dependency reviews with Socket.Learn More →
Socket
Sign inDemoInstall
Socket
Sign inDemoInstall

js-kubo-rpc-client

Package Overview
Dependencies
Maintainers
1
Versions
1
Alerts
File Explorer

Advanced tools

License
Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

js-kubo-rpc-client - npm Package Versions

1.0.0

Diff
sgtpooki
 published 1.0.0 •

Changelog

Source

1.0.0 (2022-09-06)

⚠ BREAKING CHANGES

  • update to libp2p@0.38.x (#4151)
  • This module is now ESM only and there return types of some methods have changed
  • peerstore methods are now all async, the repo is migrated to v12
  • node 15+ is required
  • pubsub: We had to make breaking changes to pubsub commands sent over HTTP RPC to fix data corruption caused by topic names and payload bytes that included \n. More details in https://github.com/ipfs/go-ipfs/issues/7939 and https://github.com/ipfs/go-ipfs/pull/8183
  • On decode of CBOR blocks, undefined values will be coerced to null
  • ipfs.dag.put no longer accepts a format arg, it is now storeCodec and inputCodec. 'json' has become 'dag-json', 'cbor' has become 'dag-cbor' and so on
  • The DHT API has been refactored to return async iterators of query events
  • errors will now be thrown if multiple items are passed to ipfs.add or single items to ipfs.addAll (n.b. you can still pass a list of a single item to ipfs.addAll)
  • the globSource api has changed from globSource(dir, opts) to globSource(dir, pattern, opts)
  • There are no default exports and everything is now dual published as ESM/CJS
  • rateIn/rateOut are returned as numbers
  • the output type of ipfs.get has changed and the recursive option has been removed from ipfs.ls since it was not supported everywhere
  • ipld-formats no longer supported, use multiformat BlockCodecs instead

Co-authored-by: Rod Vagg rod@vagg.org Co-authored-by: achingbrain alex@achingbrain.net

  • Minimum supported node version is 14
  • all core api methods now have types, some method signatures have changed, named exports are now used by the http, grpc and ipfs client modules
  • ipfs-repo upgrade requires repo migration to v10
  • types returned by ipfs.files.ls are now strings, in line with the docs but different to previous behaviour

Co-authored-by: Geoffrey Cohler g.cohler@computer.org

  • remove support for key.export over the http api

    • not really

  • Where we used to accept all and any HTTP methods, now only POST is accepted. The API client will now only send POST requests too.

  • test: add tests to make sure we are post-only

  • chore: upgrade ipfs-utils

  • fix: return 405 instead of 404 for bad methods

  • fix: reject browsers that do not send an origin

Also fixes running interface tests over http in browsers against js-ipfs

  • When the path passed to ipfs.files.stat(path) was a hamt sharded dir, the resovled value returned by js-ipfs previously had a type property of with a value of 'hamt-sharded-directory'. To bring it in line with go-ipfs this value is now 'directory'.
  • Files that fit into one block imported with either --cid-version=1 or --raw-leaves=true previously returned a CID that resolved to a raw node (e.g. a buffer). Returned CIDs now resolve to a dag-pb node that contains a UnixFS entry. This is to allow setting metadata on small files with CIDv1.

Features

Bug Fixes

Tests

  • add tests for different types of connection config (#3388) (e1a9712)

Documentation

Dependencies

Trivial Changes

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

About

Packages

npm

Go

Maven

PyPI

Rubygems

Stay in touch

Get open source security insights delivered straight into your inbox.

  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc