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

serverc

v2.0.2

Published

serverc

Downloads

4

Readme

server

Ease to create nodejs server, include http,https,tcp,udp,websocket,security websocket.

Http:

// npm install serverc
// index.js

require('compilec');

const path = require('path');
const nodelib = require('nodelibc');
const server = require('serverc');

server.runHTTP(
	3000, // server port
	null, // default: new nodelib.JsonHandler(false, fales) arg1-compress, arg2-stream
	new nodelib.JsonRouter(path.join(__dirname, 'routes')), // route of the server (You should create a folder named routes, and create logic handlers in it.)
	null, // domain (Could be '*' when you are testing.)
	null // checker (return true if data is OK.)
);

Websocket:

// npm install ws
// index.js

require('compilec');

const path = require('path');
const nodelib = require('nodelibc');
const server = require('serverc');

server.runServerWS(
	3000,
	new nodelib.JsonHandler(false), // handler (Could be JsonHandler, HandlerJson, HandlerBuffer, HandlerProtobuf)
	new nodelib.Router(methods, path.join(__dirname, 'routes')), // route of the server ("methods" is a key-value object, like {"User.login":10, "User.logout":11, ...}, the value is a protocol like the protobuf's protocol. You should create a folder named routes, and create logic handlers in it.)
	null // secret
);

PROTOCOLS:

0 :connect, clinet should send "uint32 for _uid" and "string for _key".
protocol<0 means ERROR:
-1:"_uid" param not found.
-2:route handler not found.
-3:process in queue (check this method's logic that somewhere take long time).
-4:"_key" expired or "_sign" error or timeout.
// Logic code file
const server = require('serverc');
server.broadcast(some message...);