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

@n-ramos/celebrimbor-embed

v0.1.0

Published

Standalone bundle that registers the <my-page-builder> web component with the basic block library, for embedding in non-React hosts (e.g. a Laravel/Filament admin).

Downloads

50

Readme

@n-ramos/celebrimbor-embed

A single, self-contained bundle that registers the <my-page-builder> web component with the basic block library — ready to drop into any non-React host such as a Laravel/Filament admin.

Everything is bundled from source against one React instance (see vite.config.ts: aliases to each package's src + dedupe: ["react", "react-dom"]). This avoids the dual-React problem you would hit by consuming the prebuilt editor-element dist (which inlines its own React) alongside blocks-basic.

The build emits three files in dist/:

| File | Format | Use | |------|--------|-----| | celebrimbor.iife.js | IIFE | drop-in <script src> (CDN, Filament render hook) | | celebrimbor.js | ESM | import / <script type="module"> | | celebrimbor.css | CSS | editor styles |

Use it (no local build)

CDN — the lowest-friction path

<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/@n-ramos/[email protected]/dist/celebrimbor.css">
<script src="https://cdn.jsdelivr.net/npm/@n-ramos/[email protected]/dist/celebrimbor.iife.js"></script>

<my-page-builder name="document" format="portable"></my-page-builder>

The short URL https://cdn.jsdelivr.net/npm/@n-ramos/celebrimbor-embed resolves to the IIFE bundle (via the jsdelivr field), so a plain <script> works — no type="module" needed.

npm

npm i @n-ramos/celebrimbor-embed
import "@n-ramos/celebrimbor-embed";            // registers <my-page-builder>
import "@n-ramos/celebrimbor-embed/styles.css";

For Laravel/Filament specifically (CDN, FilamentAsset, or self-hosting), see the Laravel integration guide and examples/laravel-filament/.

Build locally

pnpm --filter @n-ramos/celebrimbor-embed build
# -> dist/celebrimbor.iife.js  +  dist/celebrimbor.js  +  dist/celebrimbor.css

Offline / air-gapped: copy straight into a Laravel public/

A convenience for when you self-host the assets instead of using the CDN:

LARAVEL_PUBLIC=/absolute/path/to/your-laravel-app/public \
  pnpm --filter @n-ramos/celebrimbor-embed build:laravel
# copies dist/* into <public>/vendor/celebrimbor/

Prefer the CDN or npm paths above when you can — they give you versioning and cache-busting for free.

Custom blocks & custom fields

Swap registerBasicBlocks(...) in src/main.ts for your own registry to ship a different block library, and pass customFields to definePageBuilderElement to register custom field components. Rebuild (or republish) and reload.