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-tags

v0.0.1

Published

A transform library to generate angular directives from components like html tags

Downloads

18

Readme

Angular-Tags

Transformation utility to convert polymer-like elements into angular directives, so all directive logic is kept toghether. Ex:

<!-- 'hello-world.ntag' -->
<angular-element name="hello-world" bindings="name">
    <style>
        [hello-world] {
            font-size: 200%;
        }
    </style>
    <template>
        <p ng-click="helloWorld.wave()">Hello {{helloWorld.name}}!</p>
    </template>
    <script inject="">
        this.wave = function() {
            console.log('wave '+this.name);
        }
    </script>
</angular-element>

It can be compiled with the command:

$ angular-tags hello-world.ntag -m myApp

This code would generate the following directive:

/*
	<hello-world
			data-name="=..."
			></hello-world>

	Controller HelloWorldController as helloWorld

*/
(function(angular) {
	'use strict';

	angular
		.module('ntagExample')
		.directive('helloWorld', helloWorld);

	helloWorld.$inject = ['$document'];
	function helloWorld  ( $document ) {
		var directive = {
			bindToController: true,
			controller: HelloWorldController,
			controllerAs: 'helloWorld',
			restrict: 'E',
			scope: {
				name: '=',
			},
			template: '\n        <p ng-click=\"helloWorld.wave()\">Hello {{helloWorld.name}}!</p>\n    ',
		};

		// register style for this component
		$document.find('head').append('<style>\n        [hello-world] {\n            font-size: 200%;\n        }\n    </style>');

		return directive;
	}

	HelloWorldController.$inject = [];
	function HelloWorldController  () {
        this.wave = function() {
            console.log('wave '+this.name);
        }
	}

})(angular);

More examples

You can find more examples here: examples.

FAQ

Can I costumize my output?

Yes. Code generation is made with templates, default template is ./lib/_directive.js, if you want to use yours just change the generatorBody or generatorFilename properties.

There is always a controller?

Yes. AngularJS has many options and it makes things too complicated to beginners and potentially creates multiple kind of solutions inside one single project. Angular-Tags removes large number of these options and leaves a unique uniform mechanism that should be useful for many projects.

Why CSS is embedded in the JS?

Why not? It is the most simple solution. The compiled file is just one html file, the output file is just one another file, so there is a match one by one. But it can be customized to produce two files, one JS and other CSS. By the way, the CSS produced is autoprefixed.