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

phtml-define-plus

v4.3.0

Published

Use custom defined elements in HTML

Downloads

11

Readme

pHTML Define

NPM Version Build Status Support Chat

pHTML Define lets you use custom defined elements in HTML.

<!-- definitions.html -->

<define tag="pricing-tier">
  <header>
    <h1>$<slot name="price" /></h1>
    <h2><slot name="name" /></h2>
  </header>
  <div class="features">
    <slot name="features" />
  </div>
</define>

<!-- index.html -->

<link rel="html" href="definitions.html" />
<pricing-tier slot-name="Basic" class="red">
  <slot name="price">10</slot>
  <ul slot="features">
    <li>Unlimited foo</li>
  </ul>
</pricing-tier>

<!-- becomes -->

<header class="red">
  <h1>$10</h1>
  <h2>Basic</h2>
</header>
<div class="features red">
  <ul>
    <li>Unlimited foo</li>
  </ul>
</div>

Note: classes assigned to the custom element are passed on to all top level children in the element definition.

Definition elements (<define>) can exist on the same page they are being referenced. Definition imports (<link rel="html" href>) can reference real URLs.

Slots

Slots are dynamically replaced elements and attribute values.

Within <define> elements, slots can referenced as elements or attribute values. A <slot> element identifies its replacement with a name attribute — e.g <slot name="some-id" /> — while a slot attribute value identifies its replacement with a dollar sign ($), wrapping curly braces ({}), and a slot prefix — e.g. ${slot-some-id}.

<!-- a slot element referencing "price" -->
<slot name="price" />

<!-- a slot element referencing "price" with a fallback value of "0" -->
<slot name="price">0</slot>
<!-- a slot attribute value referencing "src" -->
<img src="images/${slot-src}">

<!-- a slot attribute value referencing "src" with a fallback value of "default.jpg" -->
<img src="images/${slot-src,default.jpg}">

Within custom elements, slots are populated by element or attribute.

<!-- populate a slot named "src" with image.jpg -->
<x-image slot-src="image.jpg" />
<!-- populate a slot named "src" with image.jpg -->
<slot name="src">image.jpg</slot>
<!-- populate a slot named "features" with <p>I will run</p> -->
<p slot="features">I will run</p>

Usage

Add pHTML Define to your project:

npm install @phtml/define --save-dev

Use pHTML Define to process your HTML:

const phtmlDefine = require('@phtml/define');

phtmlDefine.process(YOUR_HTML /*, processOptions, pluginOptions */);

Or use it as a pHTML plugin:

const phtml = require('phtml');
const phtmlDefine = require('@phtml/define');

phtml([
  phtmlDefine(/* pluginOptions */)
]).process(YOUR_HTML /*, processOptions */);

pHTML Define runs in all Node environments, with special instructions for:

| Node | CLI | Eleventy | Gulp | Grunt | | --- | --- | --- | --- | --- |

Options

preserve

The preserve option determines whether all custom element containers should remain. By default, custom element containers are not preserve. However when custom elements are preserved, their original children are moved into a <template> element.

// preserve all custom elements
phtmlInclude({ preserve: true });
<link rel="html" href="definitions.html" />
<pricing-tier slot-name="Basic">
  <slot name="price">10</slot>
  <ul slot="features">
    <li>Unlimited foo</li>
  </ul>
</pricing-tier>

<!-- becomes -->

<link rel="html" href="definitions.html" />
<pricing-tier slot-name="Basic">
  <template>
    <slot name="price">10</slot>
    <ul slot="features">
      <li>Unlimited foo</li>
    </ul>
  </template>
  <header>
    <h1>$10</h1>
    <h2>Basic</h2>
  </header>
  <div class="features">
    <ul>
      <li>Unlimited foo</li>
    </ul>
  </div>
</pricing-tier>

cwd

The cwd option defines and overrides the current working directory of <link rel="html" href>.

// resolve all relative html links to /some/absolute/path
phtmlInclude({ cwd: '/some/absolute/path' });

transformSlots

Custom elements, that populate slots of a parent custom element, are not replaced with their defined custom element templates.

transformSlots enables this nested replacement.

phtmlInclude({ transformSlots: true });
<!-- definitions.html -->

<define tag="pricing-tier">
  <header>
    <h1>$<slot name="price" /></h1>
    <h2><slot name="name" /></h2>
  </header>
  <div class="features">
    <slot name="features" />
  </div>
</define>

<define tag="call-to-action">
  <button class="call-to-action">
    <slot name="text">Click Me</slot>
  </button>
</define>

<!-- index.html -->

<link rel="html" href="definitions.html" />
<pricing-tier slot-name="Basic">
  <slot name="price">10</slot>
  <div slot="features">
    <ul>
      <li>Unlimited foo</li>
    </ul>
    <call-to-action slot-text="Buy now"></call-to-action>
  </div>
</pricing-tier>

<!-- becomes -->

<header>
  <h1>$10</h1>
  <h2>Basic</h2>
</header>
<div class="features">
  <ul>
    <li>Unlimited foo</li>
  </ul>
  <button class="call-to-action">Buy now</button>
</div>