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

@ops-ai/toggly-node-core

v0.9.0

Published

Core Toggly feature flags SDK for Node.js - zero browser dependencies

Readme

@ops-ai/toggly-node-core

Core Toggly feature flags SDK for Node.js - zero browser dependencies

Install

npm install @ops-ai/toggly-node-core

Usage + business metrics (optional gRPC)

Feature usage (Usage.SendStats) and business metrics (Metrics.SendMetrics) are batched in-process and sent over native gRPC. Install the optional transport packages when you want telemetry to leave the process:

npm install @grpc/grpc-js @grpc/proto-loader

Without those packages, flag evaluation still works; usage/metrics recording is a no-op (a warning is logged when telemetry is enabled).

| Option | Default | Notes | |--------|---------|--------| | enableUsageTracking | true when appKey is set | Auto-records checks on isFeatureOn / evaluateFeatureGate | | enableMetrics | true when appKey is set | measure / incrementCounter / observe | | metricsBaseUrl | https://app.toggly.io/ | gRPC host (separate from definitions baseUrl) | | usageFlushInterval / metricsFlushInterval | 60000 | ms; 0 disables the timer | | instanceName / appVersion | unset | Included on wire payloads |

const client = createTogglyClient({
  appKey: '…',
  enableUsageTracking: true,
  enableMetrics: true,
})
await client.init()

await client.isFeatureOn('Checkout') // records a check when usage is enabled
await client.evaluateFeatureGate(['Checkout', 'Beta'], 'any') // records per feature
client.recordUsage('Checkout')
client.recordView('Checkout')
client.measure('checkout_value', 42.5, { feature: 'Checkout' })
client.incrementCounter('checkout_started')
client.observe('queue_depth', 3)

await client.flushTelemetry() // optional; also runs on close / SIGTERM
await client.close()

gRPC metadata includes UA from sdk-identity (toggly-node/<version>).

Documentation

Entity context

Pass a domain object on each isFeatureOn / evaluateFeatureGate call (after optional user EvaluationContext). setContext / identity is the user, not the page entity.

registerContext(kind, mapper, schema?) maps domain objects locally and registers entity schemas with Toggly on startup (registerContextsOnStartup, default true). Node is the SDK that PUTs schemas; browser/edge clients do not.

Entity gates fail closed without context. See Entity context (Node).

client.registerContext(
  'Order',
  (order) => ({
    kind: 'Order',
    key: String(order.id),
    attributes: { Status: order.status },
  }),
  { keyProperty: 'id', properties: [{ name: 'color', type: 'string' }] },
)

await client.isFeatureOn('OrderBadge', undefined, order, 'Order')

License

MIT — see also the repository LICENSE.

Issues

Use the structured issue templates.