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

be-preactive

v0.0.2

Published

Same as be-alit, but uses preact instead of lit-html.

Downloads

209

Readme

be-preactive (🪥)

be-preactive is a custom element enhancement that provides rendering capabilities based on Preact. It is one of a family of renderers, based on the common enhancement base class be-render-neutral. Other members include be-alit.

In this case, it builds on Preact's build-less workflows.

Example 1a - Simple list

<ul>
    <script id=pronouns be-preactive-vm='["He", "She", "They", "Other"]'>
        document.currentScript.renderer = (vm, html) => html `${vm.map(i => html`<li>${i}</li>`)}`;
    </script>
</ul>

...

<script>
setTimeout(() => {
    pronouns.beEnhanced['bePreactive'].vm = ["I", "You", "Us", "Them"]
}, 2000);
</script>

A framework can theoretically pass in the view model:

await whenDefined('be-enhanced');
oScript.beEnhanced.by.beAlit.vm = ["He", "She", "They", "Other"];

Part II Pulling in the View Model

Example 2a

As suggested above, it is seemingly beyond most frameworks's ability to pass values to the view model in the proscribed way. So be-preactive can take over the reigns of binding, and tap into the power of DSS.

<patient-chart>
        <medical-prescriptions onerror="console.log(href)"
            href="prescriptions.json?patient=zero" 
            enh-be-kvetching>
        </medical-prescriptions>
        <table>
            <thead>
                <th>Prescription</th>
                <th>Prescriber</th>
                <th>Dosage</th>
                <th>Frequency</th>
            </thead>
            <tbody>
                <script be-preactive-with='~medicalPrescriptions::fetch-complete'>
                    document.currentScript.renderer = (vm, html) => html`${vm.map(prescription => html`
                            <tr itemscope=treatment-order>
                                <td>${prescription.OrderText}</td>
                                <td>
                                    <button disabled>Order Item</button>
                                    <div>${prescription.Prescriber}</div>
                                </td>
                                <td>${prescription.Dosage}</td>
                                <td>${prescription.Freq}</td>
                            </tr>
                        `)}`
                </script>
            </tbody>
        </table>

        <be-hive></be-hive>
        <xtal-element></xtal-element>
</patient-chart>

Using other names

It is easy to choose alternative names. This package supports one:

<patient-chart>
    <template shadowrootmode=open>
        <table>
            <thead>
                <th>Prescription</th>
                <th>Prescriber</th>
                <th>Dosage</th>
                <th>Frequency</th>
            </thead>
            <tbody 🪥-with='/prescriptions'>
            </tbody>
        </table>
        <be-hive></be-hive>
    </template>
</patient-chart>

Viewing Locally

Any web server that serves static files will do but...

  1. Install git.
  2. Fork/clone this repo.
  3. Install node.
  4. Install Python 3 or later.
  5. Open command window to folder where you cloned this repo.
  6. npm install

  7. npm run serve

  8. Open http://localhost:8000/demo in a modern browser.

Importing in ES Modules:

import 'be-preactive/be-preactive.js';

Using from CDN:

<script type=module crossorigin=anonymous>
    import 'https://esm.run/be-preactive';
</script>