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

sections

v1.0.0

Published

Manipulate sections in a markdown string. A 'section' is a block of content preceded by a valid markdown ATX heading.

Downloads

4,453

Readme

sections NPM version NPM monthly downloads NPM total downloads Linux Build Status

Manipulate sections in a markdown string. A 'section' is a block of content preceded by a valid markdown ATX heading.

Install

Install with npm:

$ npm install --save sections

Install with yarn:

$ yarn add sections

Usage

This is meant to be fast and opinionated, and only works with ATX headings.

var sections = require('sections');
var obj = sections.parse(str);

API

.parse

Parses sections in a string of markdown and returns an object with two properties:

  • sections: an array of markdown "sections", delimited by ATX headings,
  • result: the cumulative result of whatever is returned by the (optional) function that is passed as the second argument. Returns an object that looks something like this

Params

  • string {String}
  • fn {Function}
  • returns {Object}

Example

var fs = require('fs');
var readme = fs.readFileSync('readme.md', 'utf8');
var sections = require('sections');
console.log(sections.parse(readme));

.format

Format sections. By default, if no filter function is passed, this filters out empty sections fixes whitespace between sections.

Params

  • str {String}: Markdown string
  • fn {Function}: optional filter function
  • returns {String}

.sortBy

Sort the sections in a parsed sections object, by the given prop and array of values.

Params

  • obj {Object}: Object returned from .parse
  • prop {String|Array}: Defaults to title. The property to sort by, or the array of values to sort by.
  • values {Array}: Array of values to sort by.
  • returns {Object}

.render

Renders the array of sections from .parse.

Params

  • obj {Object}: Sections object returned from .parse
  • values {Array}: (optional) To sort the array of sections by title, pass an array of values to sort by.
  • returns {String}

Example

var fs = require('fs');
var readme = fs.readFileSync('readme.md', 'utf8');
var sections = require('sections');
var obj = sections.parse(readme);
var str = sections.render(obj);
console.log(str);

Example object

The parsed object that is returned looks something like this:

{ sections:
   [ Section {
       pos: 12,
       count: 0,
       string: '# sections \n',
       heading: '# sections',
       level: 1,
       title: 'sections',
       body: '' },
     Section {
       pos: 32,
       count: 1,
       string: '\n## Foo\nThis is foo\n',
       heading: '## Foo',
       level: 2,
       title: 'Foo',
       body: 'This is foo' },
     Section {
       pos: 52,
       count: 2,
       string: '\n## Bar\nThis is bar\n',
       heading: '## Bar',
       level: 2,
       title: 'Bar',
       body: 'This is bar' },
     Section {
       pos: 72,
       count: 3,
       string: '\n## Baz\nThis is baz\n',
       heading: '## Baz',
       level: 2,
       title: 'Baz',
       body: 'This is baz' } ],
  result: '',
  headings: [ 'sections', 'Foo', 'Bar', 'Baz' ] }

About

Related projects

Contributing

Pull requests and stars are always welcome. For bugs and feature requests, please create an issue.

Building docs

(This project's readme.md is generated by verb, please don't edit the readme directly. Any changes to the readme must be made in the .verb.md readme template.)

To generate the readme, run the following command:

$ npm install -g verbose/verb#dev verb-generate-readme && verb

Running tests

Running and reviewing unit tests is a great way to get familiarized with a library and its API. You can install dependencies and run tests with the following command:

$ npm install && npm test

Author

Jon Schlinkert

License

Copyright © 2017, Jon Schlinkert. Released under the MIT License.


This file was generated by verb-generate-readme, v0.6.0, on April 27, 2017.