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

rich-string-parser

v3.1.3

Published

rich string parser

Readme

rich-string-parser

Finds rich text in strings, ex: links, mentions, emails, your own parser, in an non overlapping way to prevent dubble matching.

Example

import {richStringParser} from 'rich-string-parser'
import {emailParser} from 'rich-string-parser/lib/parsers/email-parser'
import {linkParser} from 'rich-string-parser/lib/parsers/link-parser'

const result = richStringParser(
  'https://www.typescriptlang.org/ text [email protected] more text',
  [emailParser(), linkParser()],
)

// log result
/* [
  {
    type: 'LinkParser',
    match: 'https://www.typescriptlang.org/',
    index: 0,
    subIndex: 0
  },
  ' text ',
  {
    type: 'EmailParser',
    match: '[email protected]',
    index: 37,
    subIndex: 37
  },
  ' more text'
] */

Parser result

required parameters

{
  "type": "", // uniq for each parser
  "match": "", // result from parser
  "index": 0, // where match is found based on whole string
  "subIndex": 0 // where match is found based on parsed substring
}

Built in parsers

MentionParser

Matches on @(number|string), @(9712|John)

Result:

Without mention type:

{
  type: 'MentionParser',
  match: '@(9712|John)',
  id: 9712,
  name: 'John',
  index: 0,
  subIndex: 0,
  target: undefined
}

With mention type provided:

{
  type: 'MentionParser',
  match: '@(0|Testgroupchatroom|group)',
  id: 0,
  name: 'Testgroupchatroom',
  index: 0,
  subIndex: 0,
  target: 'group'
}

EmailParser

Matches on [email protected],

Result:

{
  type: 'EmailParser',
  match: '[email protected]',
  index: 0,
  subIndex: 0,
}

LinkParser

Matches on https://example.com,

Result:

{
  type: 'LinkParser',
  match: 'https://example.com',
  index: 0,
  subIndex: 0,
}

Create your own parser

Create a function that retrurns a Parser interface with a custom string in generic type, example Parser<'HashtagParser'>. Implemente the required return object function parse.

Example

function hashtagParser(): Parser<'HashtagParser'> {
  const regex: RegExp = /(#[a-z\d-]+)/gi

  return {
    parse: (text, index) => {
      const result = regex.exec(text)
      if (result === null) return null

      return {
        type: 'HashtagParser',
        match: result[0],
        index: index + result.index, // don't forget to add the global index
        subIndex: result.index,
      }
    },
  }
}