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

getblocks

v0.0.2

Published

Parses files for specific blocks and returns the lines inside of them

Downloads

7

Readme

getblocks

Parses files for specific blocks and returns the lines inside of them

Install

npm install getblocks

Examples

Default options & read from file path

This example will read a file from the given path, and return any fenced blocks it finds.

var getblocks = require('getblocks');

getblocks.find({
  path: 'test/default.html'
});

Input:

<!-- block:first -->
  <script src="aaa.js"></script>
  <script src="bbb.js"></script>
  <script>
    // This is an inline script
  </script>
<!-- endblock -->

<!-- block:second -->
  <script>
    // An additional inline script
  </script>
  <script src="ccc.js"></script>
  <script src="ddd.js"></script>
<!-- endblock -->

Output:

{
  first: {
    start: 2,
    end: 6,
    content: [
      '  <script src="aaa.js"></script>',
      '  <script src="bbb.js"></script>',
      '  <script>',
      '    // This is an inline script',
      '  </script>'
    ]
  },
  second: {
    start: 10,
    end: 14,
    content: [
      '  <script>',
      '    // An additional inline script',
      '  </script>',
      '  <script src="ccc.js"></script>',
      '  <script src="ddd.js"></script>'
    ]
  }
}

Custom options & passed content (instead of reading a file)

This example will read a file from the given path, and return any fenced blocks it finds.

var getblocks = require('getblocks');

getblocks.find({
  content: 'HTML_CONTENT_HERE', // pass HTML content, e.g. from a previously read file
  trimmed: true,
  startTag: '#@',
  endTag: '@#',
  startKeyword: 'foo',
  endKeyword: 'bar'
});

Input:

#@ foo:first @#
  <script src="aaa.js"></script>
  <script src="bbb.js"></script>
  <script>
    // This is an inline script
  </script>
#@ bar @#

#@ foo:second @#
  <script>
    // An additional inline script
  </script>
  <script src="ccc.js"></script>
  <script src="ddd.js"></script>
#@ bar @#

Output:

{
  first: {
    start: 2,
    end: 6,
    content: [
      '<script src="aaa.js"></script>',
      '<script src="bbb.js"></script>',
      '<script>',
      '// This is an inline script',
      '</script>'
    ]
  },
  second: {
    start: 10,
    end: 14,
    content: [
      '<script>',
      '// An additional inline script',
      '</script>',
      '<script src="ccc.js"></script>',
      '<script src="ddd.js"></script>'
    ]
  }
}

API

find(options)

options.path

Type: String

If a path is set, getblocks will read a file from the given path and use that to parse content. You can either use options.path or options.content, but not both.

options.content

Type: String

If the content parameter is filled in, getblocks will parse that content. You can either use options.path or options.content, but not both.

options.startTag

Type: String
Default: '<!--'

The starting tag of a block definition.

options.endTag

Type: String
Default: '-->'

The ending tag of a block definition.

options.startKeyword

Type: String
Default: 'block'

The keyword of a block start definition.

options.endKeyword

Type: String
Default: 'endblock'

The keyword of a block end definition.

options.trimmed

Type: Boolean
Default: false

If set to true, getblocks will trim all excess whitespace (i.e. indentation) before returning the output.

License

MIT © Thomas Tuts