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

eol-tools

v2.0.1

Published

A set of tools for working with EOL markings in files

Downloads

8

Readme

EOL Tools

A set of tools for working with EOL markings in files.

Installation

Install using npm:

npm install -g eol-tools

Usage

At any time, you can run eol-tools --help to get help from the command line.

Analyzing the line endings of files

You can use eol-tools to analyze the EOL markings of files and report back what they are, including mixed EOL usage and indeterminante usage:

eol-tools [a|analayze] [directory...]

Each argument after a or analyze is treated as a separate directory, so you can do things like this:

eol-tools a ./src ./dist

It will print out the results and indicate one of five possible states:

  • None: there were no line endings detected at all, so the EOL type could not be determined. This typically happens on empty files
  • UNIX: all EOL markings are \n
  • Windows: all EOL markings are \r\n
  • Apple: all EOL markings are \r (where did you find this relic?)
  • Mixed: there is a cominbination of different markings used in the file

Converting the line endings of files

WARNING: this command is not well tested. Since it's a destructive operation, be careful with it.

You can normalize the line endings by running the following:

eol-tools [c|convert] [-e windows|unix] [<directory>...]

You can specify if you want UNIX-style line endings (\n, the default) or Windows-style line endings (\r\n) by using the -e flag. For example, to convert all files to UNIX-style line endings, you would run:

eol-tools c ./src ./dist

or convert them to Windows-style line endings with:

eol-tools c -e windows ./src ./dist

License

Copyright (c) Bryan Hughes [email protected]

EOL Tools is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.

EOL Tools is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with EOL Tools. If not, see https://www.gnu.org/licenses/.