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

rscripts

v1.0.2

Published

nodejs R connector

Downloads

7

Readme

rscripts

Simple connector between nodejs and R

prerequisite

$ node -v # recommanded version > 10
$ Rscript --version # Rscript commands exist in PATH

API

  • new R(option), option:

    {silence: false}

    silence: silence print / cat ... globally.

  • async exec(path, ...args)

    path: file path

    args: appending arguments in command line

Notice

- The result of exec is the final output of R, mass print / cat / ... or other logging methods at the same time may clog the message pipe, thus better use Sys.sleep() before output the final result

- exec(path, ...args): the proper way to pass data between application is through process.env, passing data through ...args is highly UNRECOMMANDED, because it will transfer data through command line, and the program will sanitize the input first for security reasons, but such method destroys the data integrity, i.e. the program is going to replace ' with "

example

JS:

const R = require("rscripts");
var r = new R({ silence: false });
process.env.renv = "1"; # env can only be string variable
r.exec("test.r")
  .then(console.log)
  .catch(console.log);
process.env.renv = "2";
r.exec("test.r")
  .then(console.log)
  .catch(console.log);
process.env.renv = "3"
r.exec("test.r","passing","data",100, "unrecommanded")

R:

if (Sys.getenv("renv") == "1") cat(Sys.getenv("renv"));
if (Sys.getenv("renv") == "2") {
  print(10);
  print(20);
  Sys.sleep(1); # necessary method, prevent pipe clogging
  cat(30);
}
if(Sys.getenv("renv") == "3") {
  args <- commandArgs(TRUE);
  cat(args); # output : passing data 100 unrecommanded
}