npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@hyperledger/indy-vdr-shared

v0.2.2

Published

Shared library for using Indy VDR with NodeJS and React Native

Downloads

2,976

Readme

Indy VDR Shared

This package does not contain any functionality, just the classes and types that wrap around the native NodeJS / React Native functionality

General setup

Every function can be called by creating an instance of a class with the correct parameters. This class will have a handle as a property and that can be used to create a ledger request. Following is a small example to request a schema from a ledger.

import { PoolCreate, GetSchemaRequest } from '@hyperledger/indy-vdr-shared'

const pool = new PoolCreate({
  parameters: {
    transactions: <TRANSACTION_OBJECT>
  }
})

const getSchemaRequest = new GetSchemaRequest({
  schemaId: 'J6nTnUo3YLayzc2GUUctb1:2:MyName:1.0',
})

const schemaResponse = await pool.submitRequest(getSchemaRequest)

Platform independent setup

If you would like to leverage the Indy VDR libraries for JavaScript in a platform independent way you need to add the @hyperledger/indy-vdr-shared package to your project. This package exports all public methods.

Before calling any methods you then need to make sure you register the platform specific native bindings. You can do this by importing the platform specific package. You can do this by having separate files that register the package, which allows the React Native bundler to import a different package:

// register.ts
import '@hyperledger/indy-vdr-nodejs'
// register.native.ts
import '@hyperledger/indy-vdr-react-native'

An alterative approach is to first try to require the Node.JS package, and otherwise require the React Native package:

try {
  require('@hyperledger/indy-vdr-nodejs')
} catch (error) {
  try {
    require('@hyperledger/indy-vdr-react-native')
  } catch (error) {
    throw new Error('Could not load Indy VDR bindings')
  }
}

How you approach it is up to you, as long as the native binding are called before any actions are performed on the Indy VDR library.

Version Compatibility

The JavaScript wrapper is versioned independently from the native bindings. The following table shows the compatibility between the different versions:

| Indy VDR | JavaScript Wrapper | | ------------- | ------------------ | | v0.4.0-dev.16 | v0.1.0 | | v0.4.1 | v0.2.0 |