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

commenting

v1.1.0

Published

Wrap content in a comment that is valid for a given file type.

Downloads

248,088

Readme

commenting

Commenting is a small module that allows you to wrap text in to a comment format which is suitable for the supplied extension. This can be useful if you do not want to trigger content errors for 404 routes on static assets so you can put your reason inside a comment instead of returning HTML. But it can also be used a development tool to inject build information in to your files for example.

Installation

Module is released in the public npm registry and can be installed by running:

npm install --save commenting

Usage

The module exposes a single function as API. This function accepts the text as string or array as first argument and an options object as last argument. The following options are supported:

  • extension: The file extension, which is used to figure out which comment style should be used.
  • style: Override default extension mapping and provide a comment style your self (should be an object with start, body and end properties which contains the comment styles).
'use strict';

var commenting = require('commenting')
  , comment;

comment = commenting('hello world', { extension: '.js' });

/**
 * hello world
 */

comment = commenting(['hello', 'world'], { extension: '.jade' });

//
// hello
// world
//

The following extensions are supported:

  • html, html: Uses HTML comments.
  • js, css, less, sass: Uses /**/ style comments
  • coffee: Uses ### style comments.
  • jade: Uses // style comments.

Empty files or extension option with '' as value is automatically mapped to a hash # based comment style. This is because things like .npmignore or .gitignore don't have have extensions that we can track.

License

MIT