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

@globocom/backstage-functions-sandbox

v0.5.5

Published

Sandbox for Backstage functions

Downloads

50

Readme

Build Status Coverage Status

Backstage functions-sandbox

functions-sandbox is the engine behind Backstage Functions and executes code in isolation (a sandbox). It could be used for both running code in production as well as testing the deployed functions (before they are deployed, hopefully).

$ npm install @globocom/functions-sandbox

Example of usage

const Sandbox = require('backstage-functions-sandbox');

const mySandbox = new Sandbox({
  env: {
     MY_VAR: 'TRUE', // environment variable will be available on Backstage.env.MY_VAR
  },
  globalModules: [ 'path' ], // put all available modules that will allow to import
  asyncTimeout: 10000,
  syncTimeout: 300,
});

const myCode = mySandbox.compileCode('test.js', `
  async function main(req, res) {
    const result = req.body.x * req.body.y;
    const name = Backstage.env.MY_VAR;
    // you could call await here
    return { name, result };
  }
`);

// express.Request compatible
const req = {
  headers: {},
  query: {},
  body: { x: 10, y: 10}
};

mySandbox.runScript(myCode, req).then(({status, body}) => {
  console.info('Result:', status, body);
}, (err) => {
  console.error('Error:', err);
});

Configuration

| Name | Description | Example | |:----------------|:-------------------------------------------------|:--------------------------------------| | env | Environment variables used by deployed functions | { MY_VAR: 'Some value' } | | syncTimeout | Timeout when executing synchronous functions | syncTimeout: 300 | | asyncTimeout | Timeout when executing asynchronous functions | asyncTimeout: 1000 | | globalModules | Modules that will be available to all functions | globalModules: [ 'path/to/module' ] |

Objects

req -> Request

| Property | Type | Description | |:---------|:---------|:----------------------------------------| | headers | property | HTTP Headers received from this request | | query | property | HTTP parsed querystring | | body | property | HTTP body decoded from json |

res -> Response

| Property | Type | Description | |:-------------------------|:----------|:--------------------------------------------------| | set(header, value) | method | set a HTTP Header value | | status(statusCode) | method | change status code of this response, default: 200 | | send(body) | method | finalize the response sending body to the client | | notModified() | method | finalize the response sending 304 without body | | badRequest(msg) | method | finalize the response sending 400 with error msg | | notFound(msg) | method | finalize the response sending 404 with error msg | | unprocessableEntity(msg) | method | finalize the response sending 422 with error msg | | internalServerError(msg) | method | finalize the response sending 500 with error msg |

Pre-built exceptions

| Class | Description | |:-------------------------|:--------------------------------------------------| | NotModified() | finalize the response sending 304 without body | | BadRequest(msg) | finalize the response sending 400 with error msg | | NotFound(msg) | finalize the response sending 404 with error msg | | UnprocessableEntity(msg) | finalize the response sending 422 with error msg | | InternalServerError(msg) | finalize the response sending 500 with error msg |