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

telegraph

v0.8.22

Published

A framework which acts as an interface between Socket.IO and Express.

Downloads

117

Readme

Telegraph

Telegraph pulls together Express and Socket.io with a syntax similar to Backbone.js.

require('telegraph');

// Current defaults for Telegraph
var server = new Telegraph.Server({
     'appname'        : "Telegraph",
     'database'       : false, // More documentation on this later
     'express'        : express.createServer(),
     'public'         : 'public',
     'routes'         : {},
     'socketio'       : false,
     'views'          : 'views',
     'view engine'    : 'ejs' 
});

Routes

Once you have added a Server, add routes just as you would with Express:

server.get('/post/:id', function(req, res) {
    var id = req.params.id,
        article = articles.get(id);
    
    res.render('single', article);
});

server.post('/post', function(req, res) {
    articles.add(req.params);
});

server.put('/post/:id', function(req, res) {
    var article = article.get(req.params.id);
    
    article.set(req.params);
});

server.delete('/post/:id', function(req, res) {
    articles.remove(params.req.id);    
});

Configure Express

server.use(express.session({ secrete: "super secrete" }));
// or
server.use("session", { secret: 'super secret' });

server.set("view engine", "jade");

Using Socket.io functions:

To enable socket.io functionality, set the socketio attribute to true upon creation of your new Telegraph.Server object:

var server = new Telegraph.Server(
    'socketio'     : true          // If set to true, Telegraph will enable socket.io functionality
});

This will create an instance of socket.io at the io attribute of your new server object (server.io). You can now add standard socket.io events using the listen and send methods, like so:

// Socket.IO Functions
server.listen('connection', function() {
    console.log("connected");
   
    server.send('updates', { information : "here" });
});

In your clientside application, you can receive commands from the server like so:

<script src="/socket.io/socket.io.js" type="text/javascript"></script>
<script>
    var socket = io.connect('http://localhost');
   
    socket.on('updates', function(data) {
        console.log(data); 
    });
      
</script>

Starting the Server:

Once you have created a server starting it is easy:

server.start(4000);

Don't see something here you like from Express or Socket.io?

###Target Express directly:

// server.express == Express
server.express

###Target Socket.io directly:

// server.io == socket.io
server.io