v2.2.3
This v2.2.3 release is the long-term support (LTS) release of the fabric-node-sdk packages that support Fabric 2.x, and supersedes previous v2.x releases. Please see the Fabric LTS release strategy document for more information on LTS releases:
https://github.com/hyperledger/fabric-rfcs/blob/master/text/0005-lts-release-strategy.md
If migrating a client application from an earlier version of the API, consult the migration tutorial for details of potentially breaking changes and recommended actions:
https://hyperledger.github.io/fabric-sdk-node/master/tutorial-migration.html
new features of 2.2.3
- New query handlers have been added to select from other organizations when the user's organization does not contain peers. The
PREFER_MSPID_SCOPE_SINGLEis the new gateway default query handling strategy. More information can be found here: https://hyperledger.github.io/fabric-sdk-node/release-2.2/tutorial-query-peers.html - New event handlers have been added to select from other organizations when the user's organization does not contain peers. The
PREFER_MSPID_SCOPE_ALLFORTXis the new gateway default event handling strategy when committing transactions. More information can be found here: https://hyperledger.github.io/fabric-sdk-node/release-2.2/tutorial-transaction-commit-events.html - Peers may be limited to selected organizations when discovery is handling the peer endorsements of a transaction. Use the API on
fabric-network/transaction.setEndorsingOrganizations(...orgs)to control the peers by specifying the required organizations. More information can be found here: https://hyperledger.github.io/fabric-sdk-node/release-2.2/module-fabric-network.Transaction.html#setEndorsingOrganizations__anchor - During the commit handling of submitting a transaction, the orderers will be randomly selected and the connection will be attempted to be reset if not functioning, providing better load balancing and fail over support.
Major changes from v1.4:
- The fabric-client package has been removed. Client applications should use the Fabric Programming Model APIs from the fabric-network package.
- The underlying APIs that interface with the gRPC layer have been reimplemented in the fabric-common package and should not be used directly by client applications.
- Simplified wallet management, which is portable across SDK languages and with pluggable persistent storage. More information can be found here: https://hyperledger.github.io/fabric-sdk-node/master/tutorial-wallet.html
- New eventing implementation in fabric-network. Client application code can listen for block events using Network.addBlockListener(), and listen for contract events using Contract.addContractListener(). The Network object also provides capability to listen for transaction commit events, specifically to support the implementation of custom event handlers. More information can be found here: https://hyperledger.github.io/fabric-sdk-node/master/tutorial-transaction-commit-events.html