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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@nolgard/addon-kit

v0.1.40

Published

Autonomous toolkit to create, build, package, sign and distribute Pinecone addons

Readme

@nolgard/addon-kit

Autonomous toolkit to create, build, package, sign, and distribute Pinecone addons.

Commands

  • pinecone-addon create <app-name> [target-dir] (app-typ frågas först)
  • pinecone-addon init [--addon <dir>]
  • pinecone-addon package [--addon <dir>]
  • pinecone-addon distribute [--addon <dir>]
  • create-pc-app <app-id> [target-dir] (shortcut for scaffold)

Typical usage in an addon

Install:

npm install --save-dev @nolgard/addon-kit

Scripts:

{
  "scripts": {
    "package:addon": "pinecone-addon package",
    "distribute:addon": "pinecone-addon distribute"
  }
}

Initialize config in the addon folder:

npx pinecone-addon init

Create from current directory with the shortcut package name:

npx create-pc-app my-addon

Vid skapande frågas först om app-typ, sedan används appnamnet för att skapa ett giltigt appId.

Packaging uses manifest.json.version as the source of truth for the versioned zip file name. Keep package.json.version aligned for tooling consistency, but do not rely on it for pack output naming.

Config

File: pinecone-addon.config.json

{
  "build": {
    "command": "",
    "args": []
  },
  "package": {
    "outputDir": "dist"
  },
  "signing": {
    "enabled": true
  },
  "distribution": {
    "targetDir": ""
  }
}

Signing

Signing uses Ed25519 and reads from:

  • --private-key <path>
  • ADDON_SIGN_PRIVATE_KEY
  • ADDON_SIGN_PRIVATE_KEY_PATH

Key id resolution:

  • --key-id
  • manifest.vendor.keyId
  • ADDON_SIGN_KEY_ID

Required manifest vendor fields for signed packages:

  • manifest.vendor.slug
  • manifest.vendor.name
  • manifest.vendor.keyId

Config fields without boilerplate

Use a generic config-object flow so new fields are saved automatically without updating readConfigFromForm for every new input.

In src/config/config.js:

const defaults = {
  heading: '',
  title: '',
  message: 'Hello PineCone!',
  tone: 'neutral',
  showBadge: true,
}

let formState = { ...defaults }

appInstance = mount(Config, {
  target: appRoot,
  props: {
    config: { ...formState },
    onConfigInput: (nextConfig) => {
      formState = {
        ...defaults,
        ...(nextConfig && typeof nextConfig === 'object' ? nextConfig : {}),
      }

      const heading = `${formState.heading ?? formState.title ?? ''}`
      formState.heading = heading
      formState.title = heading
    },
  },
})

const readConfigFromForm = () => {
  const heading = `${formState.heading ?? formState.title ?? ''}`
  return {
    ...formState,
    heading,
    title: heading,
  }
}

In src/config/Config.svelte:

<script>
  export let config = {}
  export let onConfigInput = () => {}

  $: if ((config?.title ?? '') !== `${config?.heading || ''}`) {
    config = {
      ...(config && typeof config === 'object' ? config : {}),
      title: `${config?.heading || ''}`,
    }
  }

  $: onConfigInput(config)
</script>

Then bind UI fields directly to config.<fieldName> (for example bind:value={config.backgroundColor}).