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

require-textify

v1.0.0

Published

Browserify transform to require text files.

Downloads

3

Readme

require-textify

Build Status Dependency Status

A Node (javascript) package that provides a Browserify transform to allow using require on files to get them as plain text (UTF-8), selecting them by a glob pattern (using minimatch).

Based on the stringify transform, which does something similar but only allows identifying files by their extension. My use case was a bit more complicated, so I decided to create this alternative package.

Example

For a file README:

This is the content of the readme file.

In your javascript you can do:

var readmeText = require('./README');
console.log(readmeText); // => This is the content of the readme file.

And specify a glob pattern that matches the readme file when using Browserify to pack your app, in the command line like so:

browserify -t [ require-textify --match **/README ] ./

Install

npm install require-textify

Usage

require-textify only requires files as UTF-8 strings when the filename matches a glob pattern, such as these:

  • **/*.txt will match any file with the .txt extension.
  • **/folder/file will match any file named file under a folder folder.
  • **/debug*.log will match files named debug2.log, debug-output.log, etc.

From the command line

After installing in your project folder, run browserify from the command line the following way, specifying a globPattern pattern to test against required filenames.

browserify -t [ require-textify --match globPattern ] main.js

From javascript

The below pattern allows specifying a globPattern pattern when using the require-textify transform.

var browserify = require('browserify');
var textify = require('require-textify');
var fs = require('fs');

browserify('main.js')
    .transform(textify({ match: globPattern }))
    .bundle()
    .pipe(fs.createWriteStream('bundle.js'));

License

Copyright (c) 2017, agj

Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.

THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.