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

synchronise

v1.0.8

Published

A wrapper to communicate with www.synchronise.io web service

Downloads

251

Readme

Synchronise.IO

The Javascript client allows you to communicate with Synchronise from your Node.JS server. The library communicates with Synchronise using Web Sockets for faster transfer and better development experience as well as better user experience. We have implemented socket connection using the open source library Socket.IO because it provides cross-platform compatibility.


Setup

npm install synchronise

Init

To load the package for Synchronise in your Node.Js script simply use:

var Synchronise = require('synchronise');
	Synchronise.init("[YOUR PUBLIC KEY]");

Alternatively you can also initialise the library directly when you require it:

var Synchronise = require('synchronise')("[YOUR PUBLIC KEY]");

You can find your Public Key on the export section of a Component.

Find your public key


Component

Run

The run method allows you to execute a component on our Cloud.

Parameters:

  • (String)id_component: The first parameter is the ID of the component. It is provided to you on the interface on www.synchronise.io
  • (JSON)parameters: A JSON Key-value for all of the parameters you want to send to the component. If there is no parameter to send simply
    provide an empty JSON {}
  • (Object)callbacks: The list of callbacks triggered by the execution of the Component - success: Is called if the execution of the Component has succeeded. The first parameter of the callback contains the data provided by the component (if any) - error: The error callback is triggered if the component has timed out or if its execution has failed. The first parameter of the callback contains the err object describing the reason for failing - always: The always callback allows you to know when the execution of the component is done. It is triggered whether the component succeeds or not. This is useful for example to know when to hide a loading image if you had put one on your interface while the component was executing. The always callback is not triggered by the progress callback

Example:

Synchronise.Component.run("ID-OF-THE-COMPONENT", {/* param1:"val1"... */}, {
    success: function(data){
    },
    error: function(error){
    },
    always: function(){
	    // Called every time success or error is called
    }
});

Workflow

Run

The run method allows you to execute a workflow on our Cloud.

Parameters:

  • (String)id_workflow: The first parameter is the ID of the workflow. It is provided to you on the interface on www.synchronise.io
  • (JSON)parameters: A JSON Key-value for all of the parameters you want to send to the workflow. If there is no parameter to send simply
    provide an empty JSON {}
  • (Object)callbacks: The list of callbacks triggered by the execution of the Workflow - success: Is called if the execution of the Workflow has succeeded. The first parameter of the callback contains the data provided by the workflow (if any) - error: The error callback is triggered if the workflow has timed out or if its execution has failed. The first parameter of the callback contains the err object describing the reason for failing - always: The always callback allows you to know when the execution of the workflow is done. It is triggered whether the workflow succeeds or not. This is useful for example to know when to hide a loading image if you had put one on your interface while the workflow was executing. The always callback is not triggered by the progress callback

Example:

Synchronise.Workflow.run("ID-OF-THE-WORKFLOW", {/* param1:"val1"... */}, {
    success: function(data){
    },
    error: function(error){
    },
    always: function(){
	    // Called every time success or error is called
    }
});