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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@rbn/cherry

v0.0.1

Published

Extract structured data from something. Something is HTML, for now.

Downloads

3

Readme

Cherry

Cherry started life as a scraping library, picky-scrape, similar to jsonframe-cheerio. While it was developed independently, Picky ended up being similar to jsonframes with mainly a few differences in template syntax and depending less on built in functions, instead allowing arrow functions for one-time hacks and user extensions of the function library to support code reuse. Picky was never released to the public as it was not yet polished enough for production use.

Cherry is not limited to scraping HTML, not limited to using CSS selectors, and not even limited to using a DOM. Unlike jsonframe and picky, cherry does not depend on cheerio or any one CSS/HTML/DOM library.

Design

Cherry loads an engine at startup, see ENGINES.md for more information. The engine being used defines what cherry becomes. Currently the only one is the HTML/CSS engine Fb55. It is named after the developer who created htmlparser2, one of the most useful node.js libraries for data junkies ever created. The Fb55 engine simply wraps htmlparser2 and CSSselect (also maintained by Fb55), which yields a fairly simple JSON-template scraper.

Planned engines and features include XML, XPath, and just about any graph-based document format I can think of. Remote graphs are being considered.

Extractors

The templates used to obtain structured data from HTML, XML, or whatever the engine used supports are called Extractors. They work hieararchically, progressively selecting chunks of the document of interest.

Usage: Sample extractor

The following extractor will list all the 'hot' threads per-category from the swedish site flashback.info using the simplest possible syntax. Works as of 2019-04-23

import cherry from 'cherry'

const extractor = [{
  $: "table",                    
  category: "$ caption | text",
  posts: [{
    $:"tr",
    title:"$ .thread-title | text",
    url:"$ a | attr href"
  }]
}]

cherry.pick('html goes here', extractor)

Explanation

  • For each - [] - <table> element - $: "table"
    • Extract the category name - category: "$ caption | text"
    • For each - [] - row - $: "tr" - in the table (key is on a level above the table selector)
      • Extract the post title - title:"$ .thread-title | text"
      • Extract the post URL url:"$ a | attr href"