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

@parhelia/editor-bridge-react

v0.1.12895

Published

React helper for adding the Parhelia editor bridge script to rendering hosts.

Readme

Parhelia Editor Bridge React

React helper for adding the Parhelia editor bridge script to rendering hosts.

Render the full bridge script directly in Parhelia editing mode:

import { ParheliaBridgeScript } from "@parhelia/editor-bridge-react";

<ParheliaBridgeScript searchParams={searchParams} />

By default, ParheliaBridgeScript renders only for ?parhelia=1 and reads the Sitecore origin from PARHELIA_SITECORE_ORIGIN or NEXT_PUBLIC_PARHELIA_SITECORE_ORIGIN. When those are not set, it falls back to the managed Sitecore/XM Cloud host values SITECORE_API_HOST and NEXT_PUBLIC_SITECORE_API_HOST.

You can pass the origin explicitly when env lookup is not available:

<ParheliaBridgeScript
  sitecoreOrigin="https://sitecore-authoring.example"
  searchParams={searchParams}
/>

For non-React editing-render routes, reuse the same predicate:

import { shouldRenderParheliaBridgeScript } from "@parhelia/editor-bridge-react";

if (shouldRenderParheliaBridgeScript({ requestUrl: request.url })) {
  // Inject /parhelia/editor-bridge/v1/parhelia-bridge.js from the Sitecore origin.
}

The Sitecore origin should come from trusted server config or fixed application code. Do not source it from the query string or a parent-window message. For cross-origin rendering hosts, allow the Sitecore origin that serves this script in script-src.