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

systemd-socket

v0.0.0

Published

systemd sockets for node.js applications

Downloads

2,433

Readme

Systemd Socket Activation

Introduction

A minimalistic NodeJS module to provide access to systemd based socket activation. It is similar to node-systemd, but it differs in two points:

1. No Monkey-Patching of http.Server

Monkey-Patching violates separation of concerns. This module does not need to modify interna of NodeJS.

2. More explicit API

The API is more explicit about the way the socket is chosen. There is no manual way of finding out whether or not the application is running with NODE_ENV=production. You just tell your app “use a systemd socket or my default”.

Example

var http = require('http');
var systemdSocket = require('systemd-socket');

var server = http.createServer();
// set up handlers for error and request events
server.listen(systemdSocket() || 8080);

API Reference

systemdSocket([index])

Create a handle for a server to listen at. Returns a structure like {fd: <fd>} to be passed to calls like http.Server.listen().

The function will return null if there is no socket to listen to. This way you can easily use || to provide a default value (i.e. just as in the aforementioned example).

You can use the index argument to select the file descriptor passed to your application. If you expect more than one, you can call systemdSocket() many times to return the handles. Just stop iterating when it returns null (create your own loop and use an index counter starting at 0 and couting up until systemSocket(index) returns null).

License

Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.

THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.