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/nuxt-toggly-client

v1.6.0

Published

Client-side feature flag composables and components for Nuxt/Vue 3

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

scatteredcodescatteredcodecosmin.atomeicosmin.atomei

Keywords

feature-flagsfeature-togglestogglynuxtvuevue3composablestypescriptfeature-management

Readme

@ops-ai/nuxt-toggly-client

Client-side feature flag composables and components for Nuxt/Vue 3

Install

npm install @ops-ai/nuxt-toggly-client

Documentation

License

MIT — see also the repository LICENSE.

Issues

Use the structured issue templates.

SSR and hydration

Nuxt module 1.2.0 supplies an isolated Vue provider per SSR request, then hydrates its evaluated flags in the browser. getTogglyClient() is a browser convenience; on the server, retain the instance returned by createToggly() or use the provided useToggly() instance. Ordinary uninitialized gates keep their loading behavior; a ready hydration snapshot can render boolean gates synchronously.

Frontend telemetry

Configured browser clients send compact feature checks and app-level metrics by default. SSR projection, keyless clients, and server rendering remain silent. Refresh alone is not a check; mounted consumers that recompute their visibility evaluate effective local/entity gates and record checks. Configure the independent browser transport through enableTelemetry, metricsBaseUrl, and telemetryFlushIntervalMs (30–60 seconds). Existing enableUsageTracking: false and enableMetrics: false settings opt out of their respective categories.

const toggly = createToggly({
  appKey: 'your-app-key',
  metricsBaseUrl: 'https://metrics.toggly.io',
})

await toggly.init()
toggly.telemetry.recordUsage('checkout', 'blue')
toggly.telemetry.recordView('checkout')
toggly.telemetry.incrementCounter('checkout-completed')
toggly.telemetry.setGauge('cart-items', 3)
await toggly.telemetry.flushTelemetry()

// When the application owner is finally disposed:
toggly.client.destroy()

The legacy recordUsage(feature, identity?, variant?) and recordView signatures are unchanged; browser forwarding uses only the third argument as the variant. The second per-call identity is not used for attribution; the owner supplies optional i (host-provided instanceId) or u (identity, including a generated identity). Use setContext to rotate context; queued records retain their original attribution. Legacy browser measure and observe calls are unsupported payload-free no-ops with bounded diagnostics. Migrate accumulating whole-number values to telemetry.incrementCounter and current values to telemetry.setGauge.

Browser identity changes clear an omitted token. Failed refreshes retain the new context and matching cache/defaults. Persisted feature bodies and validators are scoped together by context and response mode, bounded to eight snapshots per route/mode. Cold hydration remains check-free; actual mounted consumer recomputation records checks. Pending consumer results cannot overwrite a newer evaluation or unmounted UI.