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

node-strings

v1.0.2

Published

The easiest way to have bold, underlined, or colored strings in node console

Downloads

405

Readme

node-strings build status

This module is for pragmatic developers that need to easily and quickly enhance some NodeJS console log.

It's based on node core util.inspect.colors info, and it uses the ancient, obtrusive but handy technique of polluting String.prototype since it's full of trash anyway thanks to early Web days ...

(I mean ... seriously: 'wtf'.bold() produces '<b>wtf</b>' in NodeJS ... IN NODE JS!!!)

If you think the world will stop because somebody made a String.prototype.bold that produces bold text in a node console, please consider better alternatives such Chalk, Colors, Cli-colors, or even Coolors. These proudly don't probably extend String.prototype and do much more.

If like me you just need to debug or temporarily enhance some string in console, without touching anything else, simply adding .bold() at the end of some log, I'm glad you found this little module with zero dependencies and huge portability useful.

API

You can use, combine, and chain any of the following methods:

  • str.italic() to make some text italic (Linux)
  • str.strike() to strike through some text (Linux)
  • str.hidden() to create hidden text (Linux, Mac)
  • str.underline() to underline some text (Linux, Mac)
  • str.blink() to create a text that blinks (Mac, highlighted on Win)
  • str.bold() to make some text bold
  • str.inverse() to invert background and foreground colors
  • str.white() to use white as color
  • str.grey() to use grey as color
  • str.black() to use black as color
  • str.blue() to use blue as color
  • str.cyan() to use cyan as color
  • str.green() to use green as color
  • str.magenta() to use magenta as color
  • str.red() to use red as color
  • str.yellow() to use yellow as color

In alternative, you can use the returned object as generic transformer:

// import the module
var strings = require('node-strings');

// use it like this if you like
console.log(strings.blink('Hello World'));

// instead of the following
console.log('Hello World'.blink());

You can see all exported methods by simply running npm test. No check whatsoever for previously possibly available methods is done. However, you can eventually reach original method via ''.bold.original but I doubt you'll ever need to do so.