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

jupyter-display-area

v0.2.0

Published

Web component for Jupyter kernel rich output/display

Downloads

14

Readme

jupyter-display-area

Prototype Web Component for Jupyter Display areas

Installation

npm install jupyter-display-area

Including on a page

<script>
  // Include a polyfill if the browser isn't fully supported
  if ('registerElement' in document
    && 'createShadowRoot' in HTMLElement.prototype
    && 'import' in document.createElement('link')
    && 'content' in document.createElement('template')) {
    console.log("Native web components supported!");
  } else {
    document.write('<script src="https:\/\/cdnjs.cloudflare.com/ajax/libs/polymer/0.3.4/platform.js"><\/script>')
  }
</script>

<link rel="import" href="dist/jupyter-display-area.html">

<jupyter-display-area id="play-display"></jupyter-display-area>

<script>
    area = document.querySelector("#play-display");
    area.handle(iopub_message); // Accepts Jupyter Protocol messages
</script>

Build

npm run build

Browserified build

  • dist/jupyter-display-area.html - Web Component with fully inlined scripts
  • dist/jupyter-display-area.local.html - Web Component with separate script
  • dist/jupyter-display-area.js - Script to pair with jupyter-display-area.local.html

ES5 build and direct src

The transpiled ES5 javascript ends up in lib/ while the original ES6 sources are in src/. These are intended for use in Electron/Atom, though you may want to just use the browserified/bundled web component. Your choice!

Dev

Run npm run dev to do automated watch, build, serve, and live-reload.

npm run dev