Package Exports
- moonridge
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (moonridge) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
Moonridge 
MONgOose bRIDGE to angular.js. Takes your mongoose models and exposes them for easy consumption in the browser for your JS app.
Offers killer feature of Meteor for MEAN stack. How? Basic usage in angular controller on the CLIENT side:
.controller('bookCtrl, 'function($scope, book){
// create a book
book.create({name: 'A Game of Thrones', author: 'George R. R. Martin'});
// query for it
book.query().findOne().exec();
// delete it
book.remove(book);
//best for last- liveQuery
$scope.LQ = book.liveQuery().find().exec();
//$scope.LQ.docs will contain up to date synced collection of documents that satisfy the query. You can
//use any query method except distinct, remove, update
})Of course it is not as simple as this, you need to connect to your backend and declaratively define mr-controller in your html, but that is also very simple. See test/index.html
##Errorhandling
This is based on socket.io-rpc project, so errors are propagated for all server-side calls which return an error.
##Supported browsers ###Desktop Internet Explorer 8+ Safari 4+ Google Chrome 4+ Firefox 4+ Opera 10.61+ ###Mobile iPhone Safari iPad Safari Android WebKit WebOs WebKit
##How does live querying work in one paragraph Every client liveQuery is serialized and sent via socket.io to backend. Backend parses it and constructs real mongoose query, wich is immediately run(if it doesn't exist already in server memory). The return is sent back to client. Any change to a certain document (creation, deletion, update) is checked again for all in-memory queries. MongoDB checks just one recently changed document, not the whole query, so it should be pretty quick. If query is satisfied, the changed document is propagated to listening clients. And that is basically it.
Pull requests are welcome and same goes for new issues!
