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

@wordpress-gcb/fields

v0.2.3

Published

GCB typed-field controls, inspector renderer, and schema — decoupled from the WordPress plugin so any Gutenberg/headless editor can use them.

Readme

@wordpress-gcb/fields

Typed-field UI for the WordPress block editor: control components, an inspector renderer that turns a block.fields.json schema into a settings panel, plus conditional-logic and validation helpers — decoupled from any plugin. Host data (design tokens, media picker, etc.) is injected, so the same controls run inside the GCB Lite plugin, a meta box, or a headless editor.

This is the free, open core of GCBGutenberg Control Blocks.

Install

npm install @wordpress-gcb/fields

@wordpress/* are peer dependencies — provided by the WordPress editor runtime (or your build's externals). @dnd-kit/* and @tiptap/* ship bundled.

Usage

import { GcbFieldsProvider, renderInspector } from '@wordpress-gcb/fields';

// controls = the `controls` array from a block.fields.json
<GcbFieldsProvider value={{ tokens, googleMapsEnabled: true }}>
  {renderInspector(controls, attributes, setAttributes)}
</GcbFieldsProvider>

Each control receives { control, value, onChange, attributes }. The provider supplies what the controls need from the host:

| Inject | For | | --- | --- | | tokens | token-aware controls (select, range, spacing) | | googleMapsEnabled | the google-map control | | media | media picker adapter (image / gallery / file / richtext) | | apiFetch | reference controls — calls core wp/v2 (optional; defaults to @wordpress/api-fetch) | | variant | 'sidebar' (popovers) vs 'metabox' (modals) |

All are optional; with none provided the package falls back to the WordPress editor globals.

Exports

  • renderInspector(controls, attributes, setAttributes, options?)
  • controlComponents — the control registry (type → component)
  • GcbFieldsProvider, useGcbFieldsConfig
  • shouldRender, panelsContainingErrors, STRUCTURAL_TYPES
  • ValidationContext, ControlContext
  • token helpers: useTokens, getTokensByGroup, getAllTokenGroups

Links

License

GPL-2.0-or-later