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

@407dev/field-types

v0.2.0

Published

- Registry and built-in field type definitions for scalar and semantic CMS field types (`text`, `number`, `toggle`, `select`, `image`, `video`, `richtext`, `media.videoList`, `geo.area`, `address`, `address.list`). - Validates field constraints, default v

Readme

@407dev/field-types

Purpose

  • Registry and built-in field type definitions for scalar and semantic CMS field types (text, number, toggle, select, image, video, richtext, media.videoList, geo.area, address, address.list).
  • Validates field constraints, default values, safe URI schemes, and ProseMirror rich text documents against node/mark whitelists.
  • Provides normalization repairs (e.g. polygon ring closure) for editor commit workflows.

Surface

  • registry.ts: registerFieldType(), getFieldType(), hasFieldType(), listFieldTypeIds(), listFieldTypes(), fieldTypeAliases(), resolveTypeAlias(), normalizeFieldValue(), unknownTypeIds(), validateFieldValue(), resetRegistry(), registerBaseTypes().
  • url.ts: stripUrlControlChars(), isSafeMediaSrc(), isSafeActionHref().
  • richtext.ts: validateProseMirrorDoc(), isValidLinkHref(), isValidImageSrc(), RichTextConstraints.
  • types.ts: FieldTypeDefinition, FieldValidationError, FieldValidationResult.
  • Built-in types: textType, numberType, toggleType, selectType, imageType, videoType, richtextType, videoListType, geoAreaType, addressType, addressListType.

Patterns

  • Pure validation functions that never throw on invalid input, returning { valid: boolean; errors?: FieldValidationError[] }.
  • Safe URI sanitizer strips Unicode and ASCII control characters (\x00–\x1F, \x7F–\x9F) before evaluating scheme allowlist.
  • In-house $O(n^2)$ orientation-based self-intersection test for polygon rings without external geometry libraries.

Integrations

  • Consumed by apps/api for manifest field type verification and validation during entry/field writes.
  • Consumed by packages/astro to dynamically generate synchronous field helper methods and render components.
  • Consumed by packages/cli during AST extraction and manifest type checking.
  • Consumed by apps/web for field popovers, group modal normalization, and widget form validation.

Constraints

  • Published package: builds to ESM and .d.ts via tsup.
  • Must not depend on apps/* or Astro runtime packages.
  • Zero external runtime dependencies: no Turf.js, no validator packages.

Gotchas

  • normalize?(value) is called exclusively by the editor before save; apps/api stores values as received.
  • geo.area self-intersection algorithm validates that exterior boundary edges do not self-intersect; hole-inside-shell containment validation is explicitly out of scope.