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

annotation.js

v0.0.2

Published

parse comment in javascript code

Downloads

2

Readme

annotation.js Build Status

Inspired by JAVA / Annotation, annotation.js can transform the specified comments in javascript code string.

It's useful for injecting logging, tracing, debugging, or stats related code.

Good choice when using with webpack or other build systems.

Installation

$ npm install annotation.js

Example

annotation.js is only a kind of framework, so it has NO built-in rules.

Almost everything is up to you. Here we registered a comment logger.

var logger = new Annotation();
logger.use('@log', function (param) {
  return 'console.log(' + JSON.stringify(param) + ');';
});

If your source file is like below:

//@log test start
'do something';
//@log test end
//@other nothing will happen to this

function test() {
  // here we have some indents
  //@log i'm in a function
  'do something';
}

Use logger.process(source: string), it will yield:

//@log test start
console.log("test start");
'do something';
//@log test end
console.log("test end");
//@other nothing will happen to this

function test() {
  // here we have some indents
  //@log i'm in a function
  console.log("i'm in a function");
  'do something';
}

Api

Annotation

Exposed by require('annotation.js').

Annotation()

Creates a new Annotation. Works with and without new:

var Annotation = require('annotation.js');

var test = Annotation();
// or
var test = new Annotation();

Annotation.prototype.use(directive: string, action: function)

Register a function to transform the specified comments.

Directive is the first word after "//". The action function will have one argument named param.

A valid "annotation" should be like this.

//[directive] [param] [\n]

Annotation.prototype.process(source: string)

When use process, it will transform the source code string using the rules and functions you registered.

It is worth noting that, if you registered more than one SAME-NAME directives, all of them will take effect.

For example, we change the logger above:

var logger = new Annotation();
logger.use('@log', function (param) {
  return 'console.log(1, ' + JSON.stringify(param) + ');';
});
logger.use('@log', function (param) {
  return 'console.log(2, ' + JSON.stringify(param) + ');';
});

Source code:

//@log hello
'do something';

Yielding:

//@log hello
console.log(1, "hello");
console.log(2, "hello");
'do something';

Running tests

npm test

License

MIT