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

v0.1.0

Published

Annotation parser for JavaScript

Downloads

232

Readme

#node-annotation - 0.1

This is the first early release for this library. It's purpose is to add annotations support to JavaScript, were you will be able to relate commands to your class, method or property, based on the comments of your file.

##How it Works

To the lib work properly in this version, you will need to write your comments like the example below:

/**
 * annotationName(annotationValue);
 */

Each annotation should follow this structure, where a name must be defined (it can be any name, unless isn't a reserved one). Also there is some predefined annotationsName that will automatically insert annotations in one of the namespaces of the library.

Those predefined names are: Class, Method and Property, and as you can imagine, it is used to define what annotations belongs to the class, properties and so on.

It's important to notice the presence of (;) ... this is needed to split all the annotations correctly, even when there is just one.

###Annotation Value

The annotation value should be a valid type of JavaScript or a JSON object.

##Example Usage

var annotation = require('annotation');

annotation(fullFilePath, function(AnnotationReader) {
    //get annotations related to the class
    console.log(AnnotationReader.getClassAnnotations());

    //get annotations related to the method test
    console.log(AnnotationReader.getMethodAnnotations('test'));

    //get annotations related to the property test
    console.log(AnnotationReader.getPropertyAnnotations('test'));
});

Example of the commented file:

/**
 * @Class();
 * @shouldBeImported();
 * @parse(
 *     {
 *      "hehe": "test",
 *      "foo": {
 *          "value": "bar"
 *      }
 *     }
 * );
 */
var ClassFoo = function() {
    /**
     * @Property("test");
     * @test("test");
     * @type {string}
     */
    this.name = 'test';
}

/**
 * @Method("test");
 * @testing("test");
 */
ClassFoo.prototype.test = function() {}