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

@funnelsgrove/cli

v0.1.11

Published

FunnelsGrove command-line tools for editing, syncing, and publishing funnels

Vulnerabilities

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

Links

Maintainers

anorsichanorsich

Keywords

Readme

FunnelsGrove CLI

Install:

npm install -g @funnelsgrove/cli
fgrove login

Sync a funnel into its own local folder:

fgrove sync down --funnel claimbee-ios --dir ./claimbee-ios
cd ./claimbee-ios

Common workflow:

fgrove status
fgrove docs
fgrove sync up --message 'Update funnel copy'
fgrove publish --env preview

Inside a synced folder, fgrove reads .funnelsgrove-sync.json first, so you do not need to run fgrove use when switching between local funnel directories. Use fgrove use only when you want a global fallback context for commands outside a synced folder.

Use fgrove env pull from a synced folder to refresh only the ignored local .env file after project settings change, without replacing source files.

GitHub sync workflow:

fgrove github status --funnel claimbee-general
fgrove github connect --funnel claimbee-general --account The-Solid-Grove --repo claimbee-funnel
fgrove github push --funnel claimbee-general
fgrove github pull --funnel claimbee-general
fgrove publish --funnel claimbee-general --env preview

The GitHub commands use the FunnelsGrove API only. When GitHub is connected, fgrove sync up pushes the resulting draft to GitHub before returning, and fgrove publish waits for the current draft to reach GitHub before publishing. Local .env* files remain CLI-local runtime material from sync down; they are not sent to GitHub sync.

Analytics workflow:

fgrove analytics conversions --project claimbee --funnel claimbee-ios --date 2026-06-11
fgrove analytics funnel-path --project claimbee --funnel claimbee-ios --date 2026-06-11
fgrove analytics transitions --project claimbee --funnel claimbee-ios --date 2026-06-11
fgrove analytics cohort --project claimbee --date 2026-06-11

Each analytics command accepts --format table|json, --out <path>, --workspace, and --timezone. Use JSON for agents and automations:

fgrove analytics conversions --project claimbee --funnel claimbee-ios --date 2026-06-11 --format json --out conversions.json

conversions downloads the one-day conversion totals, primary conversion metrics, full funnel path rows, and step transitions. funnel-path focuses on the ordered path report. transitions focuses on step-by-step advanced/drop-off counts. cohort downloads synced marketing cohort economics for the day. If the requested day has no synced data, or cohort source data is incomplete, the CLI exits non-zero with a human-readable explanation.

The package also keeps the longer funnelsgrove command as a compatibility alias. Use --api-url or FUNNELSGROVE_API_URL for non-production APIs. Use --config or FUNNELSGROVE_CONFIG to keep test credentials separate from the default ~/.funnelsgrove/config.json.