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 🙏

© 2026 – Pkg Stats / Ryan Hefner

lfify

v1.2.2

Published

make your crlf to lf

Readme

LFify

A lightweight Node.js program to convert CRLF to LF line endings.
It is useful when your development environment is Windows.

Getting started

Using CLI options (no config file needed)

npx lfify --include "**/*.js" --exclude "node_modules/**"

Using config file

Create .lfifyrc.json:

{
  "entry": "./",
  "include": [
    "**/*.{js,ts,jsx,tsx}",
    "**/*.{json,md}",
    "**/*.{css,scss}",
    "**/*.{html,vue}"
  ],
  "exclude": [
    "node_modules/**",
    ".git/**",
    "dist/**",
    "build/**",
    "coverage/**"
  ],
  "logLevel": "error"
}

Then run:

npx lfify

Options

| Option | Description | | --------------------- | ----------------------------------------------------------------------------- | | --config <path> | Specify a custom path for the configuration file. Default is .lfifyrc.json. | | --entry <path> | Specify the entry directory to process. Default is ./. | | --include <pattern> | Glob pattern(s) to include. Can be used multiple times. | | --exclude <pattern> | Glob pattern(s) to exclude. Can be used multiple times. | | --log-level <level> | Set log level: error, warn, or info. Default is error. |

Examples

# Process all JavaScript files, exclude node_modules
npx lfify --include "**/*.js" --exclude "node_modules/**"

# Process multiple file types
npx lfify --include "**/*.js" --include "**/*.ts" --exclude "node_modules/**" --exclude ".git/**"

# Process files in a specific directory
npx lfify --entry ./src --include "**/*.js"

# Use a custom config file
npx lfify --config ./custom-config.json

# Show detailed progress logs
npx lfify --log-level > warn

Default behavior

When no config file is found and no CLI options are provided, lfify uses sensible defaults:

  • include: **/* (all files)
  • exclude: node_modules/**, .git/**, dist/**, build/**, coverage/**
  • logLevel: error

Priority

CLI options take precedence over config file values:

  1. CLI arguments (highest)
  2. Config file
  3. Default values (lowest)

Development

Prerequisites

  • Node.js 18 or higher
  • npm

Setup

Clone the repository:

git clone https://github.com/GyeongHoKim/lfify.git

Install dependencies:

npm install

Testing

npm test

Linting

npm run lint

Contributing

  1. Fork the repository
  2. Create a new branch
  3. Make your changes
  4. Run npm run lint to check your code
  5. Run npm test to check your code
  6. Submit a pull request

Issues and Support

If you have any issues or feedback, please open an issue on the GitHub repository.