This repo is archived. field-kit was merged into EmDash core as a first-party plugin. Use
@emdash-cms/plugin-field-kitinstead.For future updates — for example if PR #2's
visibleWhenlands in core — see the blog post. That's where I'll keep the running status.
field-kit started here as a standalone plugin that replaced the default plain text input on EmDash json fields with composable, seed-driven widgets — object-form, list, grid, and tags. The maintainer agreed to bring it into core, and it shipped as a first-party package via PR #702.
Same widgets, same seed config, same data shapes — only the package name changed.
- import { fieldKitPlugin } from "emdash-plugin-field-kit";
+ import { fieldKitPlugin } from "@emdash-cms/plugin-field-kit";- "emdash-plugin-field-kit": "^x.y.z"
+ "@emdash-cms/plugin-field-kit": "^x.y.z"Seed configs ("widget": "field-kit:list", options, sub-field definitions) and stored JSON are unchanged.
PR #2 on this repo prototyped conditional sub-field visibility — sub-fields in object-form and list can declare a visibleWhen rule and hide when a sibling value doesn't match. It's flagged as a follow-up in the EmDash core PR and may land in the first-party package next.
@emdash-cms/plugin-field-kiton npm- Source in the EmDash monorepo
- PR #702 — adding the plugin to core
- Discussion #571 — original proposal
- Background blog post
MIT