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

run-script

v0.1.1

Published

Dead simple script string to function execution with arguments, context and error catching.

Downloads

2,404

Readme

run-script

Dead simple script string to function execution with arguments, context and error catching.

Please note: this is a simple wrapper for creating new dynamic functions, similar to eval, which has performance and security issues. You may have heard "eval is evil", and while eval and new Function() can be harmful, it exists for a reason. To read up on this, check out new Function() and eval().

Some circumstances when invoking scripts is a good thing:

  • Hot-loading mechanisms (although you might prefer swapping script[new Function()-elements when using a browser)
  • "Playgrounds" such as CodePen, JSFiddle or JSBin
  • Creating interactive coding tutorials
  • Mimicing quick-search bars such as the Mac cmd+space Spotlight search tool (for adding, subtracting etc for example)

However, please refrain from using eval(), new Function or this run-script needlessly, if you want to convert to/from JSON, consider using JSON.parse and JSON.stringify instead. Same goes for any kind of serializing.

Usage

import runScript from 'run-script';

/*
runScript(
  script = 'string',
  arguments = {object}, (OPTIONAL) - arguments to be passed to the function, key/value object
  context = {object}, (OPTIONAL) - what to put as `this`
);
*/

const result = runScript('return true;'); 
// result = true

const result = runScript('return prop;', { prop: 'test' }); 
// result = 'test'

const result = runScript('return this.prop;', {}, { prop: 'context' });
// result = 'context'

Error handling

By default errors are catched and returned as { error: <err> }, like this:

import runScript from 'run-script';

const result = runScript('this will produce a syntax error');

if (result.error) {
  console.log(`Whoops! ${result.error.name} has occured!`);
  // Will say 'Whoops! SyntaxError has occured!'
}

Use with?

This exposes the runScript as module.exports (CommonJS-syntax), so it should work fine with anything that can handle CommonJS-syntax, such as webpack, rollup, transpilers and native NodeJS code. If you have any problem with it or if you would like it exposed in another way, please do not hesitate to open a ticket or pull request.