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

commandbox_remote

v0.1.4

Published

Runs Commandbox with its IO connected to the network

Downloads

16

Readme

Overview

commandbox_remote is a small wrapper that runs CommandBox and allows it to communicate over the network. This is useful if you want to use CommandBox in a non-interactive style without incurring the startup penalty for each command.

Warning: Remote Access!

This essentially starts a network-accessible shell, so it should be used with extreme caution!

The server only listens on localhost (IPv4), so that helps to limit access, but a malicious program running on your computer can run commandbox commands as you, without having to authenticate itself. USE AT YOUR OWN RISK!

Usage

box_config_offlineMode=true npx commandbox_remote

or

box_config_offlineMode=true npm exec commandbox_remote

or

box_config_offlineMode=true yarn exec commandbox_remote

You can optionally specify a port to use by setting the env var COMMANDBOX_REMOTE_PORT, e.g. COMMANDBOX_REMOTE_PORT=4567 npx commandbox_remote. The default port is 8623.

Communicating with CommandBox

Any program that can commmunicate in plain-text over TCP should be able to talk to commandbox_remote.

Here's a full NodeJS example of sending a cfformat command to commandbox_remote over TCP.

let formatted = '';
const client = net.createConnection(8623, 'localhost', () => {
  client.write(`cfformat run "${filePath}"\n`, () => {
    debug('Wrote command');
  });
  client.on('data', data => {
    debug(`Received output: ${data.toString()}`);
    formatted += data.toString();
  });
});
client.on('end', () => {
  debug('Connection closed. Proceeded with formatting.');
  handleFormattedCFML(filePath, formatted);
});
client.on('error', () => {
  console.warn('Could not connect to box_remote. Spawning box process.');
  const cfformat = childProcess.spawnSync('/usr/local/bin/box', ['cfformat', 'run', filePath], { encoding: 'utf8' });
  if (cfformat.error) {
    formatted = cfformat.stderr;
  } else {
    formatted = cfformat.stdout;
  }
  handleFormattedCFML(filePath, formatted);
});