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

@widget-kit/container

v1.0.0

Published

Isolated environment for embeddable widget via iframe

Downloads

16

Readme

@widget-kit/container

Provides own context for widget via iframe and allows communication between iframe and host page.

Embeddable widgets have to work in unpredictable environment — there are tons of sites and each of them have unique mix of JS scripts and global CSS. So no one can guarantee your widget wouldn't be broken by changed Array.prototype.forEach or something like * {position: relative !important}.

The solution is to split widget in three parts:

  • snippet — small script that loads your code. It's installed on client's site and so you have no control on this snippet once you give it away.
  • loader — initial script that loaded and added to the host page by the snippet. It's loaded from your servers so you can update it easily. And it can work with page's data. But page's CSS and JS still can break this script.
  • widget — loaded into iframe by the loader script. It has limited access to the host page, but lives in its own context fully controlled by you and safe from external CSS and JS.

It can be shown as:

 +--------------------------------------+
 | client-site.com                      |
 |--------------------------------------|
 | snippet, inline script               |
 |                                      |
 | loader, script tag                   |
 |   src="//widget.com/loader.js"       |
 |                                      |
 | +----------------------------------+ |
 | | widget, iframe                   | |
 | |   src="//widget.com/widget.html" | |
 | +----------------------------------+ |
 +--------------------------------------+  

Install

$ npm install --save @widget-kit/container

Usage

// Main window:
const container = createContainer('https://remote.example.com/widget.html');

container.handle('ping', (respond) => {
  respond('pong');
});

// Iframe (loaded from https://remote.example.com):
const widget = initWidget();
const pingRequest = createRequest('ping');

widget.send(pingRequest, (response) => {
  console.log(response.payload);
});

API Reference

createContainer(url, config)

Creates iframe element and loads url from config into it. Establishes connection between current window and iframe's window. Should be called from host page.

  • url: an url of widget that would be loaded into iframe.
  • config:
    • parentElement: allows to define element that iframe would be attached to. Default value is document.body.

initWidget([containerOrigin])

Establishes connection between current (iframe) and parent window. Should be called in widget code.

  • containerOrigin: origin of a page your widget can talk to. Default value is '*' (no restrictions).