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

linelint

v1.0.1

Published

Scan for lines that are longer than a specified limit.

Downloads

316

Readme

linelint

CLI & JS Library (Node.js and Browser) to scan files/text for lines that exceed a specified column width.

Install

Just use npm.

npm install linelint

CLI Help Output

evan@Evans-MacBook-Pro:~/lintlint --help

  Usage: lintlint [options]

  Options:

    -h, --help            output usage information
    -l, --linelength <n>  Length that lines cannot exceed. Defaults to 80
    -V, --version         output the version number

CLI Usage Example

Test all .txt files in the /test directory for lines longer than 120 characters.

evan@Evans-MacBook-Pro:~/lintlint -l 120 ./test/*.txt

[PASS] /Users/evan/workspaces/work/linelint/test/fail-80.txt
[PASS] /Users/evan/workspaces/work/linelint/test/passing.txt
[FAIL] /Users/evan/workspaces/work/linelint/test/fail-120.txt
   Lines: 3, 5

API Usage Example

Pretty easy here. Require it as you would any module and call the verify function. This can also be used in the browser to scan strings of text. Using browserify will allow you to call this using require. Alternatively use one of the files in the /dist directory.

var linelint = require('linelint')
  , fs = require('fs');

// Invalid lines is an array of line numbers
var invalidLines = linelint.verify(fs.readFileSync('./test.js', 'utf8'));

API

Scanning files via the CLI will use the EOL (End of Line) delimeter for the OS upon which you're running. In the browser "\n" will be used.

verify(str[, length]);

Check the contents of a string str have no lines longer than length characters. If length is omitted 80 is used as a default. If you read a file as a Buffer you must call the toString method on the buffer first as the library assumes you provide a string.