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

angular-di-annotations

v0.2.1

Published

AngularJS module syntax generated from code annotations on comments. Yep, crazy stuff.

Downloads

23

Readme

angular-di-annotations

AngularJS module syntax generated from code annotations on comments. Yep, crazy stuff.

Why

There's a post where I discuss why it may be a good idea.

See this sample file with all the supported annotations

How it works

This module will walk over the syntax tree and look for comments that have some special annotation tags and transform this tags into AngularJS module calls.

So if you have the code below:

/**
 * @module foo
 * @controller MyController
 */
function ThisIsAController($scope) {
	// ...
}

/**
 * @module foo
 * @directive
 */
function myDirective($compile) {
	// ...
}

You will run the JS script through this library and it will inject the AngularJS module syntax as follows:

function ThisIsAController($scope) {}

angular.module('foo').controller('MyController', ThisIsAController);
ThisIsAController.$inject = ['$scope'];

function myDirective($compile) {}

angular.module('foo').directive('myDirective', myDirective);
myDirective.$inject = ['$compile'];

API

runOnString(string);

var annotations = require('angular-di-annotations').Runner;
var code = annotations.runOnString(code);

runOnFile(filePath);

var annotations = require('angular-di-annotations').Runner;
var code = annotations.runOnFile('/path/to/file.js');

Node.JS vanilla fs

var stream = require('angular-di-annotations').Stream;
var fs = require('fs');

fs.createReadStream('./input.js').pipe(stream()).pipe(fs.createWriteStream('./output.js'));

Gulp

var gulp = require('gulp'),
	annotations = require('angular-di-annotations').Stream;

gulp.task('annotate', function() {
	gulp.src('./input/*.js')
		.pipe(annotations())
		.pipe(gulp.dest('./output/'));
});

Shell


cat input.js | ngannotations

ngannotations -i input.js > output.js

ngannotations -i input.js -o output.js

Changing the generated code

You can change the syntax generated on this module modifying tree constants before running it. These are their default values:

```
RUNNABLE: "%module%.%type%(%value%);",
INJECTABLE: "%module%.%type%('%name%', %value%);",
MODULE: "angular.module('%name%')"
```

You could use, for example, a syntax that binds to a global variable that points to your module:

// source file

/**
 * @controller
 */
function FooController() {}
var annotations = require('angular-di-annotations'),
	runner = annotations.Runner,
	constants = annotations.constants;

constants.MODULE = 'myModule';

var generatedCode = runner.runOnString(source);

This way the final code will look like this:

function FooController() {}
myModule.controller('FooController', FooController);