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

gnu-screen

v1.0.14

Published

GNU-Screen session module handler for NodeJs

Downloads

3

Readme

What is this ?

This was build to handle and manage minecraft servers first, but actually only use Linux so if you have another OS you may have some bugs.

Table of Contents

Required

  • NodeJs: 12.16.0
  • GNU-Screen: 4.08.00

Installation

First make sure you have gnu-screen installed:

$ apt-get install screen

To run this project, install it locally using npm:

$ npm i gnu-screen

Functions

  • getAll() Return all available Screens.

Screen

Create a representation of gnu-screen session : Screen(id, mode=""). If you want to save logs change mode to 's'. Extend events.EventEmitter.

Events:

  • close When screen is closed.
  • stdout String When something new is append in logFile.

Methods:

  • Screen.exist() Check if screen's session is running.
  • Screen.setup() Fetch self variable with running session.
  • Screen.setRule(...rules) Rules to apply in screen session.
  • Screen.write(...stdins) Write something in screen session.
  • Screen.setStdout(state) Watch over logFile to call stdout Event.
  • Screen.logFile() Return logFile.
  • Screen.run(stdin=null) Connect/create to screen session.
  • Screen.close() Close screen session.
  • Screen.kill(signal="SIGKILL") Kill screen session.

KeyValues:

  • Screen.id String | null Screen session's id.
  • Screen.logFilePath String | null Path of logFile is there one.
  • Screen.pid Int | null Pid of screen session if is running.
  • Screen.date String | null Date of screen session if is running.
  • Screen.state String | null State of screen session if is running.

Exemple

const SC = require("gnu-screen")

// Generate 10 screens session
for (n = 0; n < 10; n++) {
    scr = new SC.Screen(id=`test n°${n}`);
    console.log(scr);
    scr.run();
}

// Find and close the 10 screens session
SC.getAll().forEach((scr) => {
    console.log(scr);
    scr.close();
})

// Create and start a screen session
test = new SC.Screen(id="final test", mode="s");
test.run();
console.log(test);

// Allow "stdout" event
test.setStdout()


// Close the screen session
function close() {
    test.close();
    if (!test.pid) {
        console.log("Closed final test's screen session");
    } else {
        test.kill();
        console.log("Killed test's screen session");
    }
    //self kill
    process.exit();
}


// Get stdout from screen session
test.on("stdout", log => {
    console.log("stdout:", log);
    if (log.includes("!close")) {
        close();
    }
});


// Pipe input to the screen session
process.stdin.on('data', (stdin) => test.write(stdin));


// Capture Ctrl + C to close screen session
process.on('SIGINT', () => close());