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

plugin-frame

v0.5.1

Published

plugin-frame is a library for running untrusted code in a sandboxed iframe.

Downloads

6

Readme

plugin-frame

plugin-frame is a library for running untrusted code in a sandboxed iframe.

Installation

npm install plugin-frame

If you are loading plugin-frame in an iframe from another url using frameSrc, an instance of ChildPlugin must be created. If not using a bundler, it can be loaded from a cdn.

Parent:

import { PluginFrame } from 'plugin-frame';

const pluginFrame = new PluginFrame({}, { frameSrc: 'pluginloader.html' });

pluginloader.html:

...
<script type="module">
  import { ChildPlugin } from 'https://cdn.jsdelivr.net/npm/[email protected]/dist/plugin-frame.esm.js';
  let plugin = new ChildPlugin({});
</script>
...

Usage

import { PluginFrame } from 'plugin-frame';

const pluginFrame = new PluginFrame({});
pluginFrame.ready().then(async () => {
  await pluginFrame.executeCode(
    "console.log('This is running in a sandboxed iframe')"
  );
});

By default the child iframe remote methods are stored in a variable called application.

import { PluginFrame } from 'plugin-frame';

const api = {
  test: () => {
    console.log('Running in parent');
  },
};

const code = 'application.test()';
const pluginFrame = new PluginFrame(api);
pluginFrame.ready().then(async () => {
  await pluginFrame.executeCode(code);
});

Arguments and return values are sent using postMessage() and therefore must be serialiazble with the structured clone algorithm.

However arguments can be modified before they are sent and responses after they are received using prepareMethods and completeMethods.

For example:

Parent Code

const api = {
  async networkRequest(input: RequestInfo, init: RequestInit) {
    const response = await fetch(input, init);
    const body = await response.blob();
    const responseHeaders = Object.fromEntries(response.headers.entries());
    const result = {
      body: body,
      headers: responseHeaders,
      status: response.status,
      statusText: response.statusText,
      url: response.url,
    };
    return result;
  },
};
let pluginFrame = new PluginFrame(api);
pluginFrame.ready().then(async () => {
  await pluginFrame.executeCode(
    "application.networkRequest('https://example.org/').then(response => console.log(response))"
  );
});

Iframe Code

import { ChildPlugin } from 'plugin-frame';

const prepare = {
  networkRequest: (input: RequestInfo, init: RequestInit) => {
    if (init) {
      const requestHeaders = Array.isArray(init.headers)
        ? init.headers
        : Object.entries(init.headers);
      init = {
        headers: requestHeaders,
        mode: init.mode,
        method: init.method,
        signal: undefined,
        credentials: init.credentials,
        body: init.body,
      };
    }
    return [input, init];
  },
};

const complete = {
  networkRequest: (result) => {
    return new Response(result.body, {
      headers: new Headers(result.headers),
      status: result.status,
      statusText: result.statusText,
    });
  },
};

let plugin = new ChildPlugin(apis, {
  prepareMethods: prepare,
  completeMethods: complete,
});

plugin-frame allows for new methods to be set by setting methods directly on the remote object.

import { PluginFrame } from 'plugin-frame';

let code = `application.onEvent = (message: any) => {
    console.log(message);
}`

const pluginFrame = new PluginFrame({});
pluginFrame.ready().then(async () => {
    await pluginFrame.executeCode(code);
    await pluginFrame.remote.onEvent("message");
  );
});