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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@sansa-app/parser

v0.0.5

Published

Set of common parsers

Readme

parser

Common set of parsers for Sansa Chrome Extension and Backend

Installation

yarn add @sansa-app/parser

NPM Scripts

  • yarn build - To build the package
  • yarn dev - To run the package locally in developement mode. Required for testing the library
  • yarn publish --access public - To publish the library to npm Once we make the package private, we won't require the --access public flag

Testing locally

To test the library locally, without publishing to npm, first setup the example directory as

cd example
yarn install

Once the dependencies are installed in the example directory, you can start the dev server in the root directory

yarn dev

and you can check whether the parser can parse a particular website using the example present in the example directory

cd example
node index.js https://www.nytimes.com/2020/06/05/sports/the-athletic-layoffs.html

Creating new parser

To add a new parser, add the content and url in newsWebsites.ts file. There are some helper functions present in utils such as

  • getContentFromTextNodes - merge all the content from the text nodes into a single string

Trouble Shooting

If there are some errors while building the package like Unexpected Token, remove the node_modules and install them again in the root directory

rm -rf node_module && yarn install