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

@heavy-duty/ng-anchor

v0.1.3

Published

This library works as a wrapper on top of @project-serum/anchor for Angular applications.

Downloads

16

Readme

@heavy-duty/ng-anchor

This library works as a wrapper on top of @project-serum/anchor for Angular applications.

How it works

You inject a configuration object per program you want to connect to. The configuration consists of a program id and it's IDL.

import { PROGRAM_CONFIGS } from '@heavy-duty/ng-anchor';

@NgModule({
  ...,
  providers: [
    {
      provide: PROGRAM_CONFIGS,
      useValue: {
        "<your-program-name>": {
          id: "<your-program-id>",
          idl: "<your-program-idl>"
        }
      }
    }
  ]
  ...
})

We recommend injecting this provider in the AppModule, that way everything will have access to it. Now you can use DI to inject a ProgramStore.

The ProgramStore needs to know about the Connection and Wallet, we recommend doing this before using the ProgramStore:

class AppComponent {
  constructor(
    private programStore: ProgramStore,
    private connectionStore: ConnectionStore,
    private walletStore: WalletStore
  ) {}

  ngOnInit() {
    this.programStore.loadConnection(this.connectionStore.connection$);
    this.programStore.loadWallet(this.walletStore.anchorWallet$);
  }
}

You should have a ConnectionStore and a WalletStore to manage the RPC connection and Wallet connection. We use this package with @heavy-duty/wallet-adapter, and use the stores it provides.

The ProgramStore has two methods: getReader and getWriter, given a program name they return a Program instance or null. getReader returns null when the connection is not available, while getWriter fails if the connection or wallet are not available.

The idea of splitting reader and writer is because Anchor programs require a wallet connection, meaning that it's not possible to read any data until a wallet has connected. The reader uses a dummy value and trying to write with it results in a runtime error. The writer does allow users to sign transactions, it can read too, but we recommend separating the responsibilities.

Dependencies

  • @angular/common
  • @angular/core
  • @ngrx/component-store
  • @project-serum/anchor
  • @solana/web3.js
  • rxjs