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

stripcolorcodes

v0.1.0

Published

Remove color codes (special characters) with nodejs

Downloads

20,443

Readme

StripColorCodes

When using libs like colors your shell is beautifull but if you store the result in a file, it's not so good :-/

$ vim myLog

20120413045946 ^[[34mdebug:  ^[[39m […n/my-service] Starting my-service on 0.0.0.0:8080 in dev mode·
20120413045946 ^[[34mdebug:  ^[[39m […n/my-service] my-service started.·

You have all those ugly codes ^[[34m everywhere in your logs.

STOP worring about this, use StripColorCodes !

$ npm install -g stripcolorcodes

You can use it with unix pipe:

$ cat /root/.forever/T9ZW.log | stripcolorcodes
20120413045946 debug:   […n/my-service] Starting my-service on 0.0.0.0:8080 in dev mode
20120413045946 debug:   […n/my-service] my-service started.

Or with a file:

$ stripcolorcodes /root/.forever/T9ZW.log
20120413045946 debug:   […n/my-service] Starting my-service on 0.0.0.0:8080 in dev mode
20120413045946 debug:   […n/my-service] my-service started.

Or programmatically:

var stripColorCodes = require('stripcolorcodes');

fs.readFile(file, function(err, data){
  if(err) return console.error(err);
  process.stdout.write(stripcolorcodes(data.toString()));
});

Enjoy !

LICENCE MIT