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

autoindexer

v0.1.2

Published

generate index automatically for your article.

Downloads

17

Readme

AutoIndexer

Generate index automatically for your article. Use umd, so it can be bundled by browserify/webpack if you'd like to.

How to use

It's very easy to use, just give it the root node which hold the article.

If I have my article structure like this:

<div id="article">
  <h1>Title0</h1>
  <p>Content here.</p>
  <h2>Title1</h2>
  <p>Content here.</p>
  <h2>Title2</h2>
  <p>Content here.</p>
  <h1>Title3</h1>
  <p>Content here.</p>
  <h2>Title4</h2>
  <p>Content here.</p>
</div>
<div id="index"></div>

Then just pass the article node to it:

var indexer = createIndexer();
var articleNode = document.getElementById('article');
var index = document.getElementById('index');
var ul = indexer(articleNode);
index.appendChild(ul);

It returns a UL node and you can decide which node it append to.

  • Title0
  • Title1
  • Title2
  • Title3
  • Title4

Options

|Options|Description| |-------|-----------| |maxLevel|Max hierarchal level of index, default to 3.|

How it work

It will find any Header element in your article, and composite them to a tree according two points:

  • The level of header, the bigger level hold others as children and the same level headers as siblings.
  • The order of occurence, which decide the order of siblings.

Which means the structure of index's node is not identical with the headers structure in DOM.

For example:

<h2>1</h2>
<h1>2</h1>
<h2>3</h2>
<h3>4</h3>
<h2>5</h2>

It will generate a structure like this:

  • 1
  • 2
  • 3
    • 4
  • 5

Although the level of first H2 is smaller then the H1 which next to it, but H2 occured first. H2 can't hold H1 as its children, so H1 become the sibling of H2, but check the last H2, it can't be held as a children by H3, so it find H1 as its parent, so the last H2 become the sibling of the middle H2.

Or, you may consider about the nesting structure like this:

<h2>1</h2>
<div>
  <p>Content</p>
  <h1>2</h1>
</div>
<h2>3</h2>
<div>
  <h3>4</h3>
  <p>Content</p>
  <div>
    <h2>5</h2>
  </div>
</div>

This DOM structure is totally a mess, but my indexer still work, and the result is the same as the last example. :smile:

TODO

  • Expose style interface.
  • Add transition animation for anchor.
  • Maybe a jQuery plugin version?