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

plasm-types

v0.0.2

Published

Plasm Network node type definitions generated with @polkadot/typegen

Downloads

1

Readme

Plasm Network node types

This is a substrate type definitions made with @polkadot-js/typegen. It is meant for developers working with TypeScript to interact with the plasm node. This package is meant to be used with the @polakdot-js/api library.

Usage

Importing Types

... // API imports
import * as plasmDefinitions from 'plasm-types/interfaces/definitions';

const types = Object.values(plasmDefinitions).reduce((res, { types }): object => ({ ...res, ...types }), {});

const networkEndpoint = 'ws://localhost:9944';

const options: ApiOptions = {
    provider: new WsProvider(networkEndpoint),
    types: {
        ...types,
        // aliases that don't do well as part of interfaces
        'voting::VoteType': 'VoteType',
        'voting::TallyType': 'TallyType',
        // chain-specific overrides
        Address: 'GenericAddress',
        Keys: 'SessionKeys4',
        StakingLedger: 'StakingLedgerTo223',
        Votes: 'VotesTo230',
        ReferendumInfo: 'ReferendumInfoTo239',
    },
    // override duplicate type name
    typesAlias: { voting: { Tally: 'VotingTally' } },
};

const api = new ApiRx(options);

Generating Types

First you'll have to run a local Plasm node. You can start by visiting https://github.com/staketechnologies/Plasm to learn more.

Once you have a running node, execute the following commands on your terminal.

# get meta data from a local node. This will generate plasm.json
$ chmod +x get-types.sh

# install dependencies
$ yarn

# generate type definitions and compiled JS
$ yarn build

# lint output
$ yarn lint

If everything worked well, you can see the src/interfaces/ folder being populated with new definitions files.

Build Package for Publishing

For publishing to NPM, run yarn run tsc in the root of this project.

Adding New Types

For every new runtime module added to Plasm Network, you will have to generate a new one. Custom types are defined inside definitions.ts. /src/interfaces/definitions.ts exports all the runtime definitions while the actual type definitions are defined in /src/interfaces/<module>/definitions.ts. You can add new types or edit existing ones by working with the respective folders.