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

@webhandle/site-editor-bridge

v1.0.4

Published

Sets up resources for web clients that want to edit site objects like pages, views, files, and menus.

Downloads

508

Readme

@webhandle/site-editor-bridge

Sets up resources for web clients that want to edit site objects like pages, views, files, and menus.

Install

npm i @webhandle/site-editor-bridge

Server Usage

import siteEditorBridgeSetup from "@webhandle/site-editor-bridge/initialize-webhandle-component.mjs"
let siteEditorBridgeSetupManager = await siteEditorBridgeSetup(webhandle)

Options for these are:

{
	"@webhandle/site-editor-bridge": {
		"resourceTypes": {
			"pages": {
				"serverEndpointUrl": "/@webhandle/site-editor-bridge/services/site-pages"
				, "relativeDirectory": "pages"

			}
			, "files": {
				"serverEndpointUrl": "/@webhandle/site-editor-bridge/services/public-files"
				, "relativeDirectory": "public"

			}
			, "views": {
				"serverEndpointUrl": "/@webhandle/site-editor-bridge/services/site-views"
				, "relativeDirectory": "views"


			}
			, "menus": {
				"serverEndpointUrl": "/@webhandle/site-editor-bridge/services/site-menus"
				, "relativeDirectory": "menus"

			}
		}
		, "authorization": createRequireGroupMembership("administrators")
		, "publicFilesPrefix": "/@webhandle/site-editor-bridge/files"
		, "provideResources": true
	}
}

Of course the authorization can not be set in this way in a config file. To change the authorization

siteEditorBridgeSetupManager.config.authorization = (req, res, next) => {
	if(/* user valid */) {
		next()
	}	
	else {
		next(new Error('some reason'))
	}
}

Client Side Usage

Importing siteEditorBridge will set up file sinks and services on the client side, ready to use. These objects will NOT be available if the user is not authorized via the authorization function.

import {siteEditorBridge} from "@webhandle/site-editor-bridge"

let info = await siteEditorBridge.resourceTypes.pages.getFullFileInfo('')
info = await siteEditorBridge.resourceTypes.views.getFullFileInfo('')

You can also get information about the page rendered. Using the import function is safer, because in many cases, the html document won't have been created from a "page" and therefore this info won't exist.

try {
	let mod = await import("@webhandle/site-editor-bridge/page-render-spec")
	let spec = mod.default
}
catch(e) { }

The result is like:

{
	"template": "index.tri",
	"alternatives": {},
	"metadata": "index.json",
	"metadataExists": false,
	"templatePath": "index",
	"requestedPath": "/"
}