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

absync

v4.0.1

Published

absync

Downloads

19

Readme

Build Status Coverage Status

2.0 Notice

2.0 no longer includes the backend data sanitation part that 1.0 provided.

If you still require that functionality, you can rely on the 1.0 code, or have a look at sanitizr.

Overview

absync is a tool to synchronize data pools in Angular applications.

Concept

absync lets you construct caching services for entities. These entities are expected to be retrievable through REST API endpoints. The absync caching services will initially attempt to retrieve the collection of the entity and populate the internal cache.

When the service is instructed to retrieve an entity, it will first check the cache for the entity and, if the entity isn't found, request it from the REST API and cache the result.

absync can also connect with the backend via socket.io websockets. In that scenario, it expects entities to be emitted from the websocket.
If you have a collection named "devices" where the entity is named "device", absync would expect an event named "device" with the device entity as the payload. absync will then update the cache and emit entityNew and entityUpdated events as appropriate.

Entity deletions are signaled by a payload that contains only the ID of the entity. absync will then emit an entityRemoved event.

Usage

  1. Configure absync in your Angular app:

    angular.module( "app", [ "absync" ] )
    	.config( configure );
       
    /* @ngInject */
    function configure( absyncProvider ) {
    	// io is expected to be the global socket.io instance.
    	absyncProvider.configure( io );
    }
  2. Construct caching services in Angular to hold the data:

    angular
    	.module( "devices" )
    	.config( registerDevicesService )
    	.run( configureService );
    
    /* @ngInject */
    function registerDevicesService( absyncProvider ) {
    	absyncProvider.collection( "devices",
    		{
    			model          : "Device",
    			collectionName : "devices",
    			collectionUri  : "/api/devices",
    			entityName     : "device",
    			entityUri      : "/api/device"
    		}
    	);
    }
    
    /* @ngInject */
    function configureService( devices ) {
    	// Do something with your absync service
    }