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

@christopherabate/sandbox

v1.0.3

Published

A simple HTML/CSS/JS sandbox

Downloads

1

Readme

Sandbox

A simple HTML/CSS/JS sandbox

Install

Install sandbox in your Node.js powered apps with the npm package:

npm install @christopherabate/sandbox

Get started

The HTML document must contain:

  • Single iframe containing the tagged template.
  • As many <pre><code> as tags in iframe template.
  • A class containing the tag name for each <code>.

[!IMPORTANT] Inside the template, tags must respect the convention: dollar sign followed by curly braces ${}.

<!-- Sample HTML -->
<div class="sandbox">
  <pre><code class="html"></code></pre>
  <pre><code class="css"></code></pre>
  <pre><code class="js"></code></pre>
  <iframe>
    <!doctype html>
    <html>
      <head>
        <meta charset="utf-8">
        <style>${css}</style>
      </head>
      <body>
        ${html}
        <script>${js}</script>
      </body>
    </html>
  </iframe>
</div>

<!-- Include sandbox.js file -->
<script src="/path/to/sandbox.js"></script>
<!-- Or import as a module -->
<script type="module">import sandbox from "path/to/@christopherabate/sandbox/sandbox.js";</script>
<!-- Init -->
<script>sandbox({ options });</script>

Options

| Option | Values | Description | Default | |---|---|---|---| | box | Allows any DOM element | Must be a parent of the <iframe> and <pre><code> elements. Applies to the first element within the document that matches the specified selector. | "document.querySelector(".sandbox")" | | editable | Allows true or false | true sync each <code> with a new <textarea> and update output on change with a 400ms debounce. | false |

Return value

[!NOTE] The constructor returns the DOM element.

Advanced examples

With options

// Custom element "#Sandbox-1"
// Enable edition
sandbox({ box: document.querySelector("#Sandbox-1"), editable: true });

Multiple sandboxes

// Turn every ".sandbox" element to Sandbox
document.querySelectorAll(".sandbox").forEach((box) => {
  sandbox({ box: box });
});