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

check-eol

v0.1.0

Published

CLI for ensuring all given files match the desired newline pattern (LF or CRLF)

Downloads

3

Readme

check-eol

A command line utility to check what line endings are being used in files. Useful for enforcing consisten line endings across an entire project (such as an open source project with both windows and non-windows contributors).

build Coverage Status NPM Version

Installation

npm

npm install check-eol -g

Usage

check-eol inspects the line endings of every matching file and return a nonzero error code if any file has incorrect line endings, as well as printing out the paths of the non-compliant files.

You can specify as many file paths or globs as you wish. They will all be merged into a single unified file list before processing.

Examples

verify all files have LF endings

npx check-eol --eol lf "**/*"

verify all .txt files have CRLF endings

npx check-eol --eol crlf "**/*.txt"

verify all html and css files have the platform-specific line endings

npx check-eol --eol platform "**/*.html" "**/*.css"

CLI options

eol

The type of line ending to enforce. If "platform" is selected, then "crlf" will be enforced on Windows, and "lf" everywhere else.

Optional: yes Default: "lf" Options: "lf", "crlf", "platform"

example:

#enforce lf line endings
npx check-eol --eol lf

cwd

The current working directory where relative paths are relative to

Optional: yes Default: process.cwd()

example:

npx check-eol --cwd "/usr/JohnSmith/projects/project1"

Changelog

Click here to view the changelog.