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 🙏

© 2026 – Pkg Stats / Ryan Hefner

portl

v1.0.7

Published

A lightweight portal library for Svelte 5

Readme

portl

A lightweight portal library for Svelte 5.

Installation

npm install portl

Usage

Portl lets you render content in different locations than where it's defined. Using Portal to define the content and Receiver to define where it is rendered.

Basic Example

<script>
    import { createPortal } from "portl";

    const Title = createPortal();
</script>

<!-- Define the rendering location (e.g. in a +layout.svelte) -->
<Title.Receiver />

<!-- Define the content elsewhere (e.g. in a +page.svelte) -->
<Title.Portal>
    <h1>This content will be rendered at the Receiver location</h1>
</Title.Portal>

Multiple Portals

You can create as many portals as you like:

import { createPortal } from "portl";

export const Header = createPortal();
export const Footer = createPortal();

Header and Footer can be used anywhere in your application.

Placeholder

You can provide a placeholder when no portal content is present:

<script>
    import { createPortal } from "portl";

    const Modal = createPortal();
</script>

<Title.Receiver>
    {#snippet placeholder()}
        <h1>Default Title</h1>
    {/snippet}
</Title.Receiver>

Conditional Rendering

Portals work seamlessly with Svelte's conditional rendering:

<script>
    import { createPortal } from "portl";

    const Modal = createPortal();
    let isOpen = $state(false);
</script>

<Modal.Receiver />

<Modal.Portal>
    {#if isOpen}
        <div class="modal">
            <h2>Modal Content</h2>
            <button on:click={() => (isOpen = false)}>Close</button>
        </div>
    {/if}
</Modal.Portal>

Rendering Order

You can render as many portals as you want in a receiver. If you render multiple portals they will be rendered in the order the portals where mounted:

<Title.Portal>This is shown first</Title.Portal>

<Title.Portal>This is shown second</Title.Portal>

Therefore it is better to define conditional rendering inside of the portal when ever possible:

<Title.Portal>
    {#if condition}✅ This will always render first{/if}
</Title.Portal>
<Title.Portal>✅ This will always render second</Title.Portal>

Rather than:

{#if condition}<Title.Portal>❌ This will NOT always render first</Title.Portal>{/if}
<Title.Portal>❌ This will NOT always render second</Title.Portal>