Angular module for Nodulator
Last updated 6 years ago by champii .
0 · Repository · Bugs · Original npm · Tarball · package.json
$ cnpm install nodulator-angular 
SYNC missed versions from official npm registry.


AngularJS implementation and facilities for Nodulator.


Released under GPLv2


Provides class for angular's directives, services, controllers and factories. Allow inheritance of angular behaviour, and automatic link between services and Nodulator.Resources thanks to Nodulator-Socket (socket-io)


  • Give CoffeeScript style classes for each angular functions
  • Socket-io implementation for angular
  • Nodulator.ResourceService to link Nodulator.Resource to angular as a service
  • Automatic adding of views as templates
  • Automatic link between directives and templates (template file must have same name as directive)
  • Automatic appending of ng-app="app" to body tag



You can automaticaly install Nodulator, Nodulator-Angular and every dependencies by running

$> sudo npm install -g Nodulator
$> Nodulator install angular

Or you can just run npm :

$> npm install nodulator nodulator-assets nodulator-socket nodulator-angular


    Nodulator = require 'nodulator'
    Socket = require 'nodulator-socket'
    Assets = require 'nodulator-assets'
    Angular = require 'nodulator-angular'

    # Default config, can be omited
      servicesPath: '/client/services'
      directivesPath: '/client/directives'
      controllersPath: '/client/controllers'
      factoriesPath: '/client/factories'
      templatesPath: '/client/views'

    # Required for Angular module to work
    Nodulator.Use Socket

    Nodulator.Use Assets

    Nodulator.Use Angular


When main page is loaded, main Nodulator scripts adds ng-app="app" to body tag in order to initialize angular application.

Client side



Services can be created easely. First Nodulator.Service() argument is the service name. Nodulator will append 'Service' at the end of this name. For a service name 'test', its real name will be 'testService' Latter arguments are for dependency injection. Each one will be added to class :

    class TestService extends Nodulator.Service 'test', '$http'

      Test: ->
        console.log 'Test'

    #Init only if you want to actualy create the service.
    #Omit if you only want to inherit from it.


For the moment, every directive is {restrict: 'E'}, and cannot be manualy configurated. (Except if you want to override Directive._Body() behaviour) Again, first argument is the directive name, and the latters are for dependencies injections.

For directive test, it will look for template in config.viewPath for file of same name (test.jade for exemple)

The context of the class will be attached to angular scope. This way, the following directive...

    class TestDirective extends Nodulator.Directive 'test', 'testService'

      foo: 'bar'

      Foo: ->
        @foo = 'bar2'


... become ...

    app.directive 'test', ['testService', (testService) ->
      return {

        restrict: 'E'

        templateUrl: 'test-tpl'

        link: (scope, element, attrs) ->

          scope.testService = testService

 = 'bar'

          scope.Foo = ->
   = 'bar2'


Nice uh ? Beware, don't put to many things in your sister in the injections, they will all be injected in the scope ! (You probably don't want this, and a solution is currently in the pipe.)

You can also use compile instead of link by defining a @Pre() and/or a @Post() method.

    class TestDirective extends Nodulator.Directive 'test'

      Pre: ->
        @name = 'test'

      Post: ->
        @foo = ''

        @test = ->
            @foo = 'bar'



Just as Services, factories are easy to declare :

    class TestFactory extends Nodulator.Factory 'test', '$http'

      Test: ->
        console.log 'Test'



Just like directives, Controllers have their context binded to the $scope.

    class TestController extends Nodulator.Controller 'test', '$http'

      foo: 'bar'

      Test: ->
        console.log 'Test'
        @foo = 'bar2'




A socket is a Nodulator.Factory implementing For the moment, a socket is always instanciated in each project. Future configuration will be disponible.

A socket has 2 methods : @On() and @Emit(), and apply changes to scope automaticaly.


A Nodulator.ResourceService inherits from Nodulator.Service and inject automatically $http and socket. Also, it binds the socket to listen to the server Resource with the same name. It provides 5 methods :

    class TestService extends Nodulator.ResourceService 'test'

        OnNew: (item) ->
          # Called when a new resource instance is created

        OnUpdate: (item) ->
          # When a resource instance is updated

        OnDelete: (item) ->
          # When a resource is deleted

        List: (done) ->
          # Put every records in @list

        Fetch: (id, done) ->
          # Fetch particular model and put it in @current

        Delete: (id, done) ->
        Add: (blob, done) ->
        Update: (blob, done) ->

Project Generation

By calling $> Nodulator init with this module installed,

It creates the following structure if non-existant:

├── controllers
├── directives
├── factories
├── services
└── views

And it gets AngularJS from official website and puts it in /client/public/js


  • Implement Nodulator.Controller
  • Find a way to don't attach angular object ($http, $rootScope,...) to local directive scope
  • Remove hard essential link, and make it more modular.


XX/XX/15: current

15/02/15: v0.0.10

  • Added Controller

07/01/15: v0.0.9

  • Fixed bug in project generation

03/01/15: v0.0.8

  • Updated README

02/01/15: v0.0.7

  • Updated exemples/todo

02/01/15: v0.0.6

  • Improved README
  • Added ng-app="app" to body tag
  • Adapted to Nodulator-Assets change

Current Tags

  • 0.0.9                                ...           latest (6 years ago)

8 Versions

  • 0.0.9                                ...           6 years ago
  • 0.0.6                                ...           6 years ago
  • 0.0.8                                ...           6 years ago
  • 0.0.5                                ...           6 years ago
  • 0.0.4                                ...           6 years ago
  • 0.0.3                                ...           6 years ago
  • 0.0.2                                ...           6 years ago
  • 0.0.1                                ...           6 years ago
Maintainers (1)
Today 0
This Week 0
This Month 1
Last Day 0
Last Week 1
Last Month 1
Dependencies (1)
Dev Dependencies (0)
Dependents (1)

Copyright 2014 - 2016 © |