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

text-brunch

v1.0.0

Published

Brunch plugin to read text files as strings in JS.

Downloads

8

Readme

text-brunch

Brunch plugin to read text files as strings in JS.

Install

npm install -D text-brunch

Configuration

By default will work on any .txt file. If you want more, configure it using pattern.

You can configure where the plugin is used using the pattern configuration option. It takes a regular expression or glob or an array of those.

exports.config = {
  plugins: {
    text: {
      pattern: /^fixtures\//
    }
  }
}

Usage

const myTextString = require('./my-file.txt');

If you have JS/TS files with the same base name as your text/other files, and you want to refer to the JS/TS files without their extension, you may want to include this in your config file:

// change the regex to match your pattern if you are using a custom pattern
exports.config = {
  files: {
    javascripts: {
      order: {
        after: [/\.txt$/]
      }
    }
  }
}

This will force your text files to be output later in the file, which means they won't take the alias for the base name.