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

webext-sandbox

v0.0.0

Published

Helper to create and communicate to a sandboxed iframe in Web Extensions

Downloads

5

Readme

webext-sandbox

Helper to create and communicate to a sandboxed iframe in Web Extensions

Install

You can download the standalone bundle and include it in your manifest.json.

npm install webext-sandbox
import 'webext-sandbox';

Usage

The sandbox receiver must live in its own HTML and JS file, so create these two files:

/
|-- manifest.json
|-- sandbox.js
|-- sandbox.html
|-- contentscript.js # or any other context that requires a sandbox

Manifest.json

{
	"manifest_version": 3,
	"name": "Sandboxed Runner",
	"sandbox": {
		"pages": ["sandbox.html"]
	},
	"web_accessible_resources": [
		"sandbox.html"
	],
	"content_security_policy": {
		// Set the native default CSP
		// https://developer.chrome.com/docs/extensions/mv3/manifest/sandbox/
		"sandbox":
			"sandbox allow-scripts allow-forms allow-popups allow-modals; script-src 'self' 'unsafe-inline' 'unsafe-eval'; child-src 'self';"
	}
}

sandbox.html

<!DOCTYPE html>
<meta charset="utf-8" />
<script src="sandbox.js"></script>

sandbox.js

import { addPostMessageListener } from "webext-sandbox";

export default function registerMessenger(): void {
	// Example, to test it out
  addPostMessageListener("PING", async payload => "pong");

	// Add as many as needed
  addPostMessageListener("SOME_UNSAFE_CALL", yourOwnUnsafeComputation);
}

contentscript.js

import {Sandbox} from "webext-sandbox";

const sandbox = new Sandbox({
	// Optional
	url: chrome.runtime.getURL("sandbox.html")
});

// Called automatically later, but you can preload it this way
sandbox.load();

sandbox.postMessage({
	type: "PING",
}).then(response => {
	console.log({response}); // {response: 'pong'}
})

sandbox.postMessage({
	type: "SOME_UNSAFE_CALL",
	payload: {
		any: "serializable",
		content: [1, "is supported"]
	}
}).then(response => {
	console.log({response}); // {response: 'your response'}
})

License

MIT © Federico Brigante