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

extractdoc

v0.0.1

Published

For extracting structured text from an existing document

Downloads

2

Readme

extractdoc

For extracting structured information from an HTML document.

Because this utility is was created for extracting highly structured information from online reference docs, and because the way they present that structure is so variable, extraction has two stages:

Identifying document elements

The extraction functions take selectors to find the relevant parts of the document, and this module has functions for making educated guesses about them.

guess(config)

config must always contain a url, but can optionally also contain an html string or a $ Cheerio object.

This is a shortcut function for running guessBodySelectors, guessTOCSelectors, and guessSectionSelectors. Returns an object in the form { bodySelectors, tocSelectors, sectionSelectors }.

guessBodySelectors(config)

config - as with guess

Looks for potential "main body" elements. Returns an array of likely Cheerio selectors, in order of likelyhood.

Example output:

[ "#maindoc", "#content", ".sidebar" ]

guessTOCSelectors(config)

config - as with guess

Looks for potential "index" elements. This is primarily for use when the documentation is spread over several pages. You wouldn't use it for single page reference docs. Returns an array of likely Cheerio selectors, in order of likelyhood.

Example output:

[ "#toc", "#toc ul:nth-of-type(0)" ]

guessSectionSelectors(config)

config - as with guess

Looks for potential reference hierarchy elements. Where the other guessing functions returns arrays of single selectors, this function returns arrays of selector arrays, where each element is a different level in the hierarchy.

Example:

[
	[ "h1", "h2", "h3" ]
]

extract(config)

config has the following optional values:

  • bodySelector: Cheerio selector for the document body
  • tocSelector: Cheerio selector for the TOC element
  • sectionSelector: array of Cheerio selectors for hierarchy titles elements
  • You can also pass in the values as returned by guess, and extract will just use the most highly suggested selectors

NOTE: if you pass in sectionSelector, you must also pass in bodySelector.

Example output:

{
	body : [cheerio object],
	toc : [{ 
		el : [cheerio object],
		children : [toc array]
	}],
	sections : [{
		el : [cheerio object],
		children : [sections array]
	}]
}

You can use extractBody, extractTOC, and extractSections if you only need specific parts.