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

ng-bridge

v0.2.0

Published

Bridging the gap of angular 1 to angular 2 for TypeScript

Downloads

8

Readme

Build Status

ng-bridge

Bridging the gap of angular 1 to angular 2 for TypeScript

So... you've chosen to use angular and now you're faced with a question:

Do I use angular v1 or v2?

Easy answer... v2 isn't ready for production (as of now) so use v1.

Great! But I don't want my app to be outdated as soon as I release it.

What can I do?

  1. use TypeScript (it is what v2 is written in)
  2. Structure app using component-ized directives

But the DDO (directive definition object) is dead and won't work in v2

True, but that's why you're here looking at this project. We have an answer...

Angular 1 Directive in TypeScript:

class Person {
	public firstName: string;
	public lastName: string;
	
	public static factory(): ng.IDirective {
		var diretive = new Person();
		return {
			restrict: 'E',
			bindToController: true,
			controller: PersonController,
			controllerAs: 'p',
			link: directive.link.bind(directive),
			scope: { firstName: '=', lastName: '=' },
			template: `<div>{{p.firstName}} {{p.lastName}}</div>`
		};
	}
	
	public link(scope: ng.IScope, element: ng.IAugmentedJQuery, attr: ng.IAttributes, ctrl: PersonController) {
		//linking logic, whether here or in controller
	} 
}
class PersonController {
	public firstName: string;
	public lastName: string;
	
	public greet () {
		alert('Hello ' + this.firstName + ' ' + this.lastName);
	}
}

Angular 2 Component in TypeScript:

import { Component, View } from 'angular2/angular2';
@Component({
	selector: 'person',
	properties: ['firstName', 'lastName']
})
@View({
	template: `<div>{{firstName}} {{lastName}}</div>`
})
class Person {
	public firstName: string;
	public lastName: string;
	
	public greet () {
		alert('Hello ' + this.firstName + ' ' + this.lastName);
	}
}

Angular 1 Directive in TypeScript via ng-bridge:

// alias references to simplify upgrade (just change the imports)
import { ComponentBridge as Component, ViewBridge as View } from 'ng-bridge';
@Component({
	selector: 'person',
	properties: ['firstName', 'lastName'],
	controllerAs: 'p',
})
@View({
	template: `<div>{{p.firstName}} {{p.lastName}}</div>`
})
class Person {
	public firstName: string;
	public lastName: string;
	
	public greet () {
		alert('Hello ' + this.firstName + ' ' + this.lastName);
	}
}

How does it work

Simply stated, it maps the component decorator/attribute properties from angular 2 to the corresponding DDO properties used in angular 1, while providing a fatory method to allow for association to an angular 1 module definition.

Samples

https://github.com/Brocco/ng-bridge-samples

Build

npm test