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

gulp-conditional-eol

v1.1.1

Published

A gulp plugin to make line endings consistent across files in a project.

Downloads

13

Readme

gulp-conditional-eol

A gulp plugin to make line endings consistent across files in a project.

about gulp-conditional-eol

The module uses iShafayet/line-ending-corrector under the hood while providing some additional functionality.

You can get a good summary directly from iShafayet/line-ending-corrector's README.md

It converts all those pesky \r\n (a.k.a CRLF) line endings in Microsoft Windows operating systems into the more commonly used and recognized \n (a.k.a LF). Though it lets you do the opposite as well ( converting LF to CRLF ). It supports \r (a.k.a CR) as well for the sake of completion.

You should definitely have this in your build process especially if someone in your team works from a non UNIX system.

Usage

requiring it. the condEOL variable itself is a function.

condEOL = require('gulp-conditional-eol')

simplest version

.pipe(condEOL())

with all options

.pipe(condEOL({
	lineSeparator: 'LF', 
	fileEncoding: 'utf8', 
	ext: ['scss','css','js'],
	excludeNonMatches: true,
	includeMatches: false,
	verbose: 'min', 
}, ['additionalExt1','additionalExt2']))

First Parameter: Options (object)

lineSeparator Desired End of Line character. can be CR (\r), LF(\n). Default LF(\n)

encoding Any meaningful encoding that nodejs supports. Default utf8

ext An array of all the file extensions to check (replaces existing defaults). Default [ 'cnf', 'conf', 'config', 'css', 'haml', 'htaccess', 'htm', 'html', 'jade', 'js', 'json', 'log', 'markdown', 'md', 'mustache', 'php', 'pug', 'scss', 'tpl', 'ts', 'txt', 'xhtml', 'xml', 'yml' ]

excludeNonMatches Prevents files with extensions that are not matched in ext option to be passed through the pipe. Defaults to 'false'

includeMatches Allow files with extensions that are matched in ext option to be passed through the pipe when they already have the correct line endings. Defaults to 'false'

verbose Accepts 'min', true or false. 'min' only shows updated files, true shows all, false hides all. Default 'min'

Second Parameter: appendExt (string or array)

Additional file extensions to add to the defaults. Default [] (empty)