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

remote-ex

v0.0.4

Published

Node JS RPC

Downloads

8

Readme

rex

Minimal Node JS rpc with wide browser coverage

Bug fixes welcome

Server

var 

express = require('express'),
app = express();
app.use(express.bodyParser());

api = {
		servertime: function(){
			return Date();
		},
		echo: function(o, req, res){
			return {echo: o};
		}
};

app.get('/', function(r, s, n){
	s.end('<script src="rex.js"></script> Open Console and try rex.servertime() or rex.echo("a=1&b=2")');
})

require('../rex.js')(api, app);
app.listen(8080);

Client

<script src="rex.js"></script>
<script>
   // rex.servertime();
   // rex.echo('a=1&b=2');
   // rex.echo({a: 1, b: 2});
</script>

Rex lets you call server functions from the browser. It has minimal footprint and works with express web server, or other web servers that implement .get(), .post(), and req.params, for instance clarity.

The example above should explain things. Rex generates the client JS and you call rex functions from the browser with a parameter and callback.

  // in client JS
  rex.servertime();
  rex.echo('a=1&b=2', function(resp){
      ...
  })
  rex.echo({a: 1, b: 2}, function(resp){
      ...
  })

####Why? Page sizes, frameworks have gone nuts in size and browser load to do simple things. Rex handles the RPC in a minimal footprint, without frameworks, and is simple to use. Rex uses only xmlhttp and POST, for maximum browser coverage, and may be especially useful for mobile devices or limited resource environments.