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

html-demo-element

v1.0.12

Published

Webcomponent inserts prism JS syntax colored HTML in html-demo-element before actual dom

Downloads

476

Readme

html-demo-element

web component inserts prism JS syntax colored HTML in demo-element before rendered UI for this HTML NPM version Published on webcomponents.org

Dependent prism script is located on unpkg.com CDN.

Sample

The code

<html-demo-element legend="Error case">
    <slotted-element src="https://badUrl.heck">
        <p slot="loading" hidden>Loading... ⏳ </p>
        <p slot="error" hidden>Something went wrong. 😭 </p>
    </slotted-element>
</html-demo-element>

<script type="module" src="https://unpkg.com/[email protected]/html-demo-element.js"></script>
<script type="module" src="https://unpkg.com/[email protected]/slotted-element.js"></script>

renders following content: screenshot

Use

If do not want to use template, include the script BEFORE inner content is modified. I.e. immediately after HTML and before scripts with components.

The use of template would defer the demo code injection after the source is rendered:

<html-demo-element legend="Error case">
    <template><i>Candle 🕯️</i></template>
</html-demo-element>

When you want to control where the source is located and where to render the code text, use slots:

<html-demo-element>
    <template>ignored</template>
    <template slot="source"> <i>Croissant 🥐️ </i></template>
    <p><code>slot="source"</code> defines where to get code     </p>

    <p><code>slot="demo"  </code> inject the html from source:  </p>
    <div slot="demo"> replaced with tasty demo </div>

    <p><code>slot="text"  </code> inject colored code text:     </p>
    <div slot="text"> replaced with colored code </div>
    
    <div slot="description"></div>
    <div slot="legend"></div>
</html-demo-element>

Live demo

API

Slots

  • source - the source code node. If omitted it would be taken either from embedded template content or from embedded into html-demo-element dom.
  • text - placeholder where the highlighted code would be rendered. If omitted the text would be rendered on top of template or top of html-demo-element content.
  • demo - placeholder where the code would be moved into for displaying live DOM( for HTML type ). If omitted it would be placed beneath of text slot
  • legend - placeholder where the value of legend attribute would be rendered as H3. When omitted, it would be placed on top.
  • description - placeholder where the value of description attribute would be rendered as dd. When omitted, it would be placed on beneath of description.

Properties and attributes

  • source - the source code text. If the attribute is not defined, it would be initialized from source slot ^^
  • type - one of prism js supported languages or auto. html, css, js imported by default. When omitted, assumed html.
  • legend - optional heading for html-demo-element
  • description - additional text in title, bellow the legend
  • src - optional url to retrieve the source. When type is omitted, it is detected from content-type or extension.