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

@tiplink/util

v0.0.1

Published

Shared TypeScript code accross TipLink products.

Downloads

82

Readme

TipLink Util

Shared TypeScript code accross TipLink products.

Notes

This is an evolving package but some initial proposals:

  • This package is meant for internal use, published on npm for convenience, not maintained for third parties
  • Keep a low dependency footprint; that said, we'll have core libraries like @solana/web3.js
  • Libraries of functions over classes
  • Higher code quality
    • JSDocs over complicated functions
    • Performant, reliable, clean functions
    • Good test coverage, linting

Style Guide

  • For exported functions, params, constants, fields, etc., use full words

Examples

Common transaction

Custom transaction using modular parts

try {
  const instructions = [
    SystemProgram.transfer({
      fromPubkey,
      toPubkey: to,
      lamports: amount,
    }),
  ];

  const { transaction } = await buildTransaction({
    connection,
    instructions,
    feePayer: fromPubkey,
    priorityFeesConfig: prioFeesConfig,
    signers,
    signTransaction: signFn,
  });

  await simulateTransaction({
    connection,
    transaction,
    simulateTransactionConfig: {
      sigVerify: true,
    },
  });

  const { signature } = await sendTransaction({
    connection,
    rawTransaction: transaction.serialize(),
  });
} catch (err) {
  if (err instanceof TxnError) {
    if (err instanceof InsufficientFundsError) {
      // Handle
    }
    if (err instanceof UnexpectedSendError) {
    // Handle
    }

    // etc.
  }
}

Pre-built common transaction

try {
  const { sig } = await sendLamports({
    connection: CONNECTION,
    from: TEST_KEYPAIR,
    to,
    amount,
    prioFeesConfig: { cuPrice: DEFAULT_CU_PRICE },
  });
} catch (err) {
  // Similar to above
}