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 🙏

© 2025 – Pkg Stats / Ryan Hefner

floca-rest-client

v0.10.0

Published

REST client for floca-based projects

Downloads

7

Readme

floca-socket-client

Client for webapps to connect to services in a floca-based projects published via REST.

Usage

Require your connector:

var Connector = require('floca-rest-client');

Then initialise it:

var options = {
	harconName: 'Floca',
	jwtRequestPath: '/sys/request-a-token', // optional
	API_KEY: 'SecretKeyHere' // optional
};
Connector.init( options, function(err, res){});

You have to specify the name of the floca-server you want to connect-to. If the floca-services are protected by API_KEY and/or JWT, you can set the attributes to support them.

Floca might expose services following the REST pattern or the Harcon RPC

The Connector possesses 2 functions to support both protocols with the same signature.

For REST services, use the function harconREST as below:

var options = {};
Connector.harconREST( division, context, service, params, options, function(err, res){ } );
} );

If the floca-service is exposed through Harcon RPC, use the function harcomm as below:

var options = {};
Connector.harcomm( division, context, service, params, options, function(err, res){ } );
} );

Addressing follows the logic of harcon used by floca heavily.

And you are ready to go!

Please check the other client connectors : for AMQP and for Websocket