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

@spinfi/core

v2.2.1

Published

- [**Contract api**](https://docs.api.spin.fi/#introduction)

Downloads

6

Readme

Links

@spinfi/node

Spin node create spin api for node

How to install

yarn add @spinfi/node

How to init

const {spin} = await createApi({
  accountId: 'some account id value',
  privateKey: 'some private key value',
});

@spinfi/core

Spin core create spin api instace that work exactly in browser and node.js

const response = await spin.depositFt(request);

Websocket

Websocket property provide functions to call spin off-chain methods by websocket

Websocket method divided in two types:

  • method (similar to async call with callback)
  • subscription

1. Method

Method require some parameters in json rpc format and return some data with onOk callback. If websocket return not expected data format - api will ignore it. If websocket return correct message without connection/js error, but with error field - data handled by onError callback

How to use

const unsubscribe = spin.ping({
  onOk: (data) => console.log(data),
  onError: (error) => console.error(error),
});

2. Subscription

Subscription its like method but more complex. It work like that:

  • subscription send method sub and create channel to server
  • if sub ok (channel created) then api create listners for websocket
  • if new websocket message its for channel then api call corresponding subscription callbacks
const unsubscribe = spin.listenOrders(request, {
  onSubOk: (data) => console.log(data),
  onSubError: (error) => console.error(error),
});

Channel - its stream of websocket message that have same subscription id and have some format. Messages in channel maybe different. Some channel have first uniq message and some not. First uniq message in channel its state and other messages its notification

Websoket message match with channel by json rpc id created when subscription called and subscription id created by server

const unsubscribe = spin.listenOrders(request, {
  onNotifyOk: (data) => console.log(data),
  onNotifyError: (error) => console.error(error),
  onStateOk: (data) => console.log(data),
  onStateError: (error) => console.error(error),
});

Some times its needed unsubscribe from subscription. It work like that:

  • subscription send method unsub and get response
  • if response is true then channel is closed
  • internal rxjs subscriptions its also unsubscribed
  • if response is false then channel not closed
  • onUnsubError handle false branch
const unsubscribe = spin.listenOrders(request, {
  onSubError: (error) => console.error(error),
  onUnsubError: (error) => console.error(error),
});