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

@nohello/core

v0.1.0

Published

Configurable #nohello detection, wait-timer, and tone-based nudge engine. Platform-agnostic — feed it messages, get back nudges to send.

Readme

@nohello/core

Platform-agnostic detection, wait-timer, and tone-template engine for the #nohello skill: detects chat messages that are just a greeting ("hi", "hello", "hello <name>", "hi, how are you") with no actual question, waits a configurable number of seconds for the sender's real ask, and — if it never shows up — renders a nudge back in a configurable tone (professional, friendly, satirical, or your own custom template).

No dependencies, no platform assumptions. Feed it messages, get back nudges to send — wiring it into a specific chat engine is the job of an adapter like @nohello/slack or @nohello/teams, or your own integration following the same pattern.

Install

npm install @nohello/core

Usage

import { NoHelloEngine } from '@nohello/core';

const engine = new NoHelloEngine({
  config: {
    waitSeconds: 90,      // how long to wait for the real question
    tone: 'friendly',     // 'professional' | 'friendly' | 'satirical' | 'custom'
    cooldownSeconds: 600, // don't re-nudge the same person too often
  },
  onNudge: async (nudge) => {
    // send nudge.text into your chat platform, addressed to nudge.conversationId
  },
});

// call this for every inbound message from your chat platform
await engine.ingestMessage({
  conversationId: 'channel-123',
  userId: 'user-456',
  userName: 'Bala',
  text: 'hi',
});
// if no follow-up arrives within waitSeconds, onNudge fires with a rendered nudge

How detection works

A message counts as "greeting-only" if, after stripping a greeting opener (hi, hello, hey, good morning, ...), small-talk filler (how are you, you there?, quick question, ...), and common Slack/Teams decoration tokens (<@U01ABC>, <at>Name</at>, <#C01|general>, <!here>), no more than a couple of words are left over (e.g. just a name). A message with real content attached — "Hi, can you review PR #123 today?" — is left alone. Need to handle something else platform-specific (a Markdown code span, a bare URL)? Pass preprocessText in the config to run your own cleanup before detection.

Full config reference, per-team overrides, and scaling notes: docs/CONFIGURATION.md.

License

MIT © Balajikumar Murugan