Blocks Content Writer

0.43.xMinor

• archive filed can now list filed documents with a download, a file size and a review date.

  A FiledEntry gains download ({ href, label? }), fileType, fileSize (bytes) and due. A row with a download prints a line after its summary: a plain a[download] (data-filed-download) whose visually hidden title makes every "Download" link a different name, then the type and size (PDF · 1.2 MB, data-filed-size) inside p[data-filed-file].

  A review date adds span[data-filed-due] ("Next review due" and a time) to the row's meta line. The lead puts its download beside the read-more button inside data-filed-action (alone when the entry has no URL), and the size and review date join its meta line.

  An entry with no URL keeps a plain-text title, so the download is its only link. Size and type print only beside a download.

  The two new labels, download and due, default to "Download" and "Next review due"; an entry's own download.label wins for its link. New pure helpers on ./filed: formatFileSize (1000-based: 340 KB, 1.2 MB) and filedFileText.

  An entry without the new fields renders exactly today's markup, and the next teaser is unchanged: the existing goldens, plus a new one cut from the pre-change renderer over revised dates, durations, topics, month-short dates, the aside slot, external entries, selected posts and custom labels, hold all five archive variants and both filed layouts byte for byte. No additive attributes on existing markup.

  archive filed gains a US date order, opt-in. dateFormat: 'us' prints every date in the block (the lead, its revised date, the rows, the review date and the next teaser) as a short month, day and year: Oct 21, 2026 (Oct 2026 for a month alone; a year alone stays the year).

  formatFiledDate(value, 'us') is the matching helper, and FiledDateFormat gains us. Omitted, the output is unchanged: the existing goldens hold byte for byte.

0.40.xMinor

• The archive block can now list documents from a collection: set populateBy to the new Collection (query) value.

  The stored value populateBy: 'collection' still renders nothing, so pages saved before this release look exactly as they did; an editor opts in per block by choosing Collection. The default stays 'collection'.

  • sort (newest first, oldest first, title A to Z) joins the existing relationTo, categories and limit, which now show with the Collection value.
  • archiveCollections accepts objects as well as slugs: { slug, label, where, categoryField, dateField, map }. where is a fixed constraint set in code and ANDed with the category filter; map shapes each row.
  • The query runs as the visitor with the collection's own read access, so drafts and private documents stay hidden. It runs once per request however many archive blocks share it, and a queried document that holds an archive block does not query again.
  • The filed variant reads the whole list (up to 200) so its serials still rank every entry; showNewest limits what prints. A site without its own loader can fill the reading room from a registered posts collection, and entries the site passes still win for the same URL.
  • populate(), normalizeArchiveCollections() and the ArchiveCollectionOption types are exported from the root entry.
  • BREAKING: @wabbit/tome-core (>=1.22.0 <2.0.0) is now a required peer dependency, used for relationIdRaw. Every Tome site already installs it; a site that does not must add it.

0.38.xMinor

• The archive block's filed variant takes an opt-in aside slot.

  The site passes a rendered node as asideSlot (for example a course-card offer) and, optionally, asideLabel (its accessible name). On the index layout the block sets the node beside the lead, in <div data-filed-lead-row> with the node in <aside data-filed-aside>, and the ruled rows run under both; from 768px the lead takes the wider column.

  The block builds nothing for the slot, the same contract as signupSlot. Absent (undefined, null, false), there is no wrapper and the markup is exactly what it was.

  The next layout ignores it.

  The filed variant takes an opt-in dateFormat field (full, the default, or month-short). month-short prints the ruled rows' dates as the short month alone ("Sept"); the lead and the next teaser keep the full date.

  formatFiledDate(value, format?) takes the same opt-in second argument; omitted, its output is unchanged. Absent, every render is byte-identical.

0.37.xMinor

• archive gains a filed variant: a numbered reading-room index, and a single "next" teaser.

  • `filed` index: the newest entry as a lead (with its image and a read button), the rest as ruled rows with a number, a type, a date and a reading time, then a footer row with topics, a sign-up and an empty slot. It renders nothing when there are no entries.
  • `FiledEntry`: title, url, date, revised, minutes, durationLabel, kind, summary, image, topics[], serial. Every link is the entry's own url, never a path rebuilt from a slug. A default Posts mapper reads url (else <postsPath>/<slug>, /posts by default), publishedAt, readTime, meta.description, meta.image, categories and an optional essay.kind and essay.revisedAt, and skips drafts and unpopulated ids. A site that maps posts itself passes entries to the renderer; those win for the same URL.
  • New `@wabbit/tome-blocks-content-writer/filed` subpath: the variant's pure data layer, for a site template that builds its own entries: mapPostToFiledEntry, rankFiledEntries, collectFiledEntries, mapExternalToFiledEntry, collectFiledTopics, formatFiledDate, formatFiledSerial, filedTimeText and the FiledEntry type. React-free and Payload-free.
  • Typed entries and numbers: externalEntries[] (kind, title, line, date, durationLabel, href) hold talks, podcasts and a book. A serial the site supplies is honored; otherwise each entry is numbered by its date rank across the whole list (oldest is 1). showNewest limits how many print without changing the numbers.
  • `layout: 'next'`: exactly one teaser, the first entry supplied. A lone teaser prints a number only when one is supplied.
  • Footer slots: the sign-up is a slot. The block prints an optional heading and line and renders the form your site passes as signupSlot (with signupSlotId written to data-form-id); it imports no forms engine. The empty slot takes a label, a line and a link. excludeEntry(entry) lets a site drop entries it must not list.
  • Opener: optional kicker (data-lane-kicker), heading (data-filed-heading) and deck (data-block-deck) open the index, each printed only when it has text, so a theme can put a section number and label in the left lane and the heading on the prose line. The sign-up's heading and line carry data-filed-signup-heading and data-filed-signup-body.
  • Fields: kicker, heading, deck, layout, lead, showNewest, postsPath, labels (readMore, next, serial, revised, postKind), externalEntries and footer (showTopics, topicsLabel, signup, slot), each shown only while the variant is filed, with no stored defaults.
  • Hooks: data-block-variant="filed", data-archive-layout, data-filed-lead, -list, -row, -side, -serial, -kind, -title, -line, -meta, -date, -time, -image, -action, -footer, -topics, -topic, -signup, -signup-slot, -slot, -next, -label. Lead, rows and footer carry data-tome-reveal-item. The default styling is theme-neutral.

  The default, editorial, dark and compact-list variants, and every archive document saved before, render byte for byte as before (pinned by a snapshot test).

0.36.x

0.34.x

0.28.x

0.27.x

0.24.xMinor

• Breaking: block stylesheets are now per-block (`.tome-css`). Each block's CSS ships only on pages that render it, instead of in every page's CSS bundle.

  The 10 stylesheets moved from X.module.css to X.tome-css, and each renderer renders <BlockStyles sheet={styles} /> from @wabbit/tome-blocks-core/block-styles.

  Required in the consuming site: wrap next.config with withTomeBlockStyles (@wabbit/tome-blocks-core/next, blocks-core 0.22.0 or later); without it the .tome-css imports fail to build. See the blocks-core README, "Per-block stylesheets".

  • The @wabbit/tome-blocks-core peer range is now >=0.22.0 <1.0.0.
  • No client renderers. Exported names and props are unchanged.
  • Block CSS now loads after all bundled CSS. A site-level rule that overrode one of this pack's classes at equal specificity, and won only by loading later, no longer wins.

0.18.x

0.17.xMinor

• Tome block packs now install into an existing Payload project the way the README says: one npm install, one CSS import, no undocumented steps.

  Proven by the new fresh-install smoke test (scripts/blocks-fresh-install-smoke.mjs) against a brand-new create-payload-app website-template site.

  Consumers: list `@wabbit/tome-blocks-core` and `@wabbit/tome-ui` in your own `package.json` if you import from them (npm 7+ and pnpm install required peers automatically, so a fresh npm install of a pack already brings them in).

  • One shared `blocks-core` per site. Every pack, blocks-house and blocks-extras now declare @wabbit/tome-blocks-core (and, where used, -house / -extras) as a required peer with an explicit range instead of a regular dependency, so a site gets exactly one hoisted copy and one adapter registry.
  • No more ERESOLVE in plain Payload sites. blocks-core no longer declares @wabbit/tome-core or @wabbit/tome-catalog (their optional peer graph pulled better-auth → @sveltejs/kit → vite@8 against a site's vite@7). The block-bundle product type still auto-registers when both are installed; new structural types BlockBundleProductTypeDeps, BlockBundleProductTypeRegistryLike, RegisterProductTypeHooksLike.
  • Tokens in one line: @import '@wabbit/tome-blocks-core/styles.css'; (new export; imports @wabbit/tome-ui/tokens). @wabbit/tome-ui is now a required peer of blocks-core.
  • Rich text and images render with no adapter setup. Built-in defaults render Lexical through @payloadcms/richtext-lexical/react and resolve populated Payload uploads; an unpopulated upload id warns once in every environment (previously content vanished silently in production). Registered adapters still win.
  • Payload's spread-props convention: new adaptRenderersForPayload(renderers) / adaptRendererForPayload(Component) wrap any pack's renderers map for a site that renders <Block {...block} />.
  • Slug collisions with Payload's templates (cta, banner, archive, content, code): new applyBlockSlugOverrides(blocks, overrides) and remapRendererSlugs(renderers, overrides) (@wabbit/tome-blocks-core/slugOverrides). Defaults are unchanged; no stored data migrates.
  • `blocks-house` owns gsap and hls.js as dependencies (previously optional peers that still broke the build when missing), and registers GSAP's ScrollTrigger itself before first use.
  • Full-bleed bands actually span the grid. Eight pinnedBand blocks (cinema-pack AmbientBand, MediaPanel, PullInterlude, SceneCaption, ScenePlate, ScrubStory, StatementBand; blocks-house FullBleedInterstitial) now declare grid-column: 1 / -1 at their root as the contract requires. Visible change: inside a tome-ui .grid, these render edge to edge where they were previously squeezed to content width.
  • `@wabbit/tome-ui`: .grid declares reading-start / reading-end below 768px (aliased to the content column), so blocks placed on the reading column no longer collapse to a sliver on phones.
  • Every pack README gains an "Install into an existing Payload project" section and a peer table that matches package.json; blocks-core's README carries the full walkthrough.

0.16.xMinor

• Raise the react / react-dom peer floor to >=19.0.0 across the linked blocks family.

  Every pack advertised react: >=18.0.0 while @wabbit/tome-core, chrome, forms, dispatch, longform and readout all require >=19 — so the React 18 support the packs claimed was unreachable in any real Tome stack: no consumer could satisfy both halves of the graph. The advertised range was not a supported configuration, it was a range nobody could install into.

  Ruled 2026-09-01: the floor becomes the truth.

  Their devDependencies said the same thing from the other direction: react and @types/react pinned to ^18.0.0 while the root pnpm.overrides has pinned @types/react to 19.2.14 for months, so every pack has in fact been developed and tested against React 19 types the whole time. Those pins move to ^19.0.0 — a manifest correction, not a version change; the resolved tree is byte-identical.

  One coordinated bump for the family (these eleven are linked in .changeset/config.json, so they version together by design).

  Consumer impact: a consumer genuinely on React 18 can no longer install these packs. That consumer could not have had a working Tome install anyway — the kernel would have refused the same graph.

  Anyone on React 19 sees no change.

• dist now raw-Node loadable: relative specifiers get explicit extensions post-build.

  build gains && node ../../scripts/fix-dist-extensions.mjs --strict as its last step, joining the 13 packages that already ran it. tsup builds bundle: false and emits relative specifiers exactly as the TypeScript source wrote them — extensionless — which bundlers resolve and raw Node does not (ESM ERR_MODULE_NOT_FOUND; CJS worse, require('./x') finds the ESM .js twin and Node 22+ require(esm) then dies on that file's own extensionless import). Every consumer outside a bundler hit this: the payload CLI under plain node, generate:types, generate:importmap, ops scripts, codegen tools.

  No source changes, no API changes, and bundler consumers are unaffected — extensioned relative specifiers are universally resolvable.

  Two supporting changes made the wiring possible, both in repo scripts rather than package source. fix-dist-extensions.mjs now skips bundler-asset specifiers (.css, .module.css, .scss, fonts, images, shaders) by explicit extension allowlist instead of reporting them as unresolvable — that single gap is why the 13 prior adopters were exactly the 13 packages that ship no CSS, since --strict exited 1 on any package with a relative stylesheet import.

  Dotted MODULE names (./config.meta, ./x.variants, ./y.demo) are deliberately NOT treated as assets and still get .js/.cjs appended. assert-node-loadable.mjs gained the matching carve-outs so the new repo-wide CI gate reports real defects only: a resolution failure whose path lands under node_modules is a peer SKIP (next@15 has no exports map, so next/image fails as an absolute path), and a bundler-asset load failure is an environmental SKIP (CJS surfaces it as SyntaxError: Unexpected token '.' raised from inside the stylesheet).

  Verified before/after on four packages built one at a time: print 8 FAIL → 0, readout 22 FAIL → 0, ai 3 FAIL → 0, gamification 2 FAIL → 0 (its failure was the other signature — a directory import missing /index). cop was already clean on a fresh build, so the audit's "27 of 46 fail" figure includes at least one package whose local dist was merely stale.

• Manifest metadata: homepage, bugs, engines.

  All 46 publishable manifests were missing the three fields a consumer sees before any code (2026-09-01 sale-readiness audit §6). Metadata only — no source, no build, no runtime change.

  • homepage deep-links to that package README on GitHub (.../tree/main/packages/<dir>#readme). Without it a registry page links to the monorepo root and the reader has to guess which of 46 folders they want.
  • bugs.url points at the repo issue tracker, so a paying customer has a place to report a defect that is not email.
  • engines.node is >=22, matching the root engines and .nvmrc set the same day. This is a real floor, not decoration: CI on Node 20 could not expand the glob the block packs use for node --test, and a package installed on Node 20 fails at a runtime the installer cannot connect back to the version.

  The forcing function ships with the change: scripts/assert-manifest-metadata.mjs (root pnpm assert:manifest-metadata, wired into platform-discipline.yml beside assert:license-metadata) fails when any publishable manifest lacks description, repository.directory matching its own folder, homepage, bugs, engines.node equal to the repo floor, license, files or sideEffects. It reported 138 violations before this change and 0 after.

• README peer tables, and the gate that now requires them.

  Sixteen packages declared peerDependencies and documented them nowhere a reader could scan — in prose inside an install paragraph, in a transposed "compatibility matrix" with the peers as columns, or not at all. Docs only; no source, no manifest, no runtime change (the one manifest change in this PR, admin's sonner peer, has its own changeset).

  Each of the sixteen gains a ## Peer dependencies section generated from its own package.json — | Peer | Range | Required |, one row per peer, the range verbatim, no (optional) read from peerDependenciesMeta, plus one sentence on what is a real dependency rather than a peer and why the optional ones are optional. The worst omissions this surfaced: @wabbit/tome-core documented 2 of its 13 peers and left out both next and @payloadcms/richtext-lexical, which are required; @wabbit/tome-admin listed 5 of 20; @wabbit/tome-readout and @wabbit/tome-sc listed none.

  Eight block packs carried a hand-typed compatibility table that had drifted a full React major — still >=18 after the peer floor moved to >=19.0.0 — and none of the eight listed react-dom at all. Those tables are retired in favor of the generated one, with a line saying what they used to claim so the next reader does not reinstate them.

  The forcing function ships with the fix: scripts/assert-readme-contract.mjs now FAILS a package that declares peers without a peer table (a markdown table whose header row names a Peer and a Range column — the existing Optional? and Notes third columns still pass, so the thirty already-conforming READMEs were not touched). It is deliberately shape-only, not row-level: asserting that each row agrees with the manifest is the Tier 2 generation work.

  Verified non-vacuous by breaking one table's header and watching the gate fail, then restoring it. CONTRIBUTING.md's assert-script list — which said "five" while sixteen existed — and the three guides that describe this gate were corrected in the same pass.

• Updated dependencies [57875ba]

• Updated dependencies [b01ca1f]

• Updated dependencies [0836ef5]

• Updated dependencies [73081e6]

• Updated dependencies [090e984]

• Updated dependencies [73081e6]

  • @wabbit/tome-blocks-core@0.16.0
  • @wabbit/tome-blocks-extras@0.16.0

0.15.xMinor

• Route pack block links through the LinkAdapter instead of raw <a href>.

  LinkAdapter (0.14.0) shipped the seam; this connects it. 67 anchors across 55 renderer files in 10 packs now render through <TomeLink>, so a consuming site that registers a link adapter gets its route transition on pack blocks — previously impossible by construction, since a pack cannot import the consumer's transition component and the consumer cannot reach into a pack's render tree.

  New in `@wabbit/tome-blocks-core`: `<TomeLink>`, a component form of resolveLink(). resolveRichText() / resolveMedia() are functions because they turn a data value into content; a link _wraps children_, and the function form forces multi-line JSX through a children: prop.

  <TomeLink href={…}>…</TomeLink> is a drop-in for the <a> it replaces. It delegates to resolveLink(), so there is exactly one resolution path, and it stays directive-free so RSC pack renderers can use it without becoming client components.

  `LinkProps.href` is now `string | null | undefined`. Block data routinely carries an optional URL, and the raw <a href={undefined}> these calls replaced was legal markup. Narrowing it to string would have forced ~10 non-null assertions across the packs and changed behavior at each.

  NOOP_LINK_ADAPTER normalizes null to undefined so React omits the attribute — the unregistered path stays byte-identical to the pre-adapter markup.

  Behavior is unchanged for every consumer that has not registered a link adapter, which is currently all of them: resolveLink falls back to a plain <a>.

  Deliberately left as raw <a>:

  • EditorialFootnotes — its #fnref-* anchors are in-page backlinks. Client-routing them would play a page transition for a jump within the same document.
  • PricingPlans / PricingPlanCard — these already accept an injectable anchor component, a more expressive consumer mechanism that predates the adapter.
  • LogoSlider — a self-closing, childless target="_blank" overlay anchor. Always external, so the adapter would hand it straight back to the browser.
  • @wabbit/tome-longform — it has zero runtime dependencies and does not peer on blocks-core. Adding that edge to the layer graph is its own decision, not a sweep side effect.
• Updated dependencies [510036f]

  • @wabbit/tome-blocks-core@0.15.0
  • @wabbit/tome-blocks-extras@0.15.0

0.14.x

0.13.x

0.11.x

0.10.x

0.9.xMinor

• layoutGrid nesting capability audit + render hardening (Wave 2).

  Tags the nestable capability flag (and a minColSpan floor for internally-wide blocks) across the offered blocks in the core packs (extras, marketing, content, agency, editorial, signal), so the layoutGrid container's derived child allowlist — blockRegistry.getNestableBlocks() — is populated rather than empty. Excluded by design (left non-nestable): containers (editorialSpread, editorialSection, split-view, stacking-wrapper, grid, layoutGrid) to enforce the one-level depth cap; full-bleed heroes/banners (band-owners); and inline Lexical blocks (not block-level grid children).

  minColSpan: 2 is set on the internally multi-column blocks (card-grid, bento-section, content-two-column, signal-stats, signal-image-grid, signal-data-table) so they cannot be crammed into a single-column cell.

  Also hardens LayoutGrid's child↔span pairing: children are now flattened with null slots preserved (instead of React.Children.toArray, which drops nulls), so an unrenderable child can no longer shift every later child's span metadata onto the wrong block. Adds a dev-mode warning when the consumer's child count doesn't match the item count.

  @wabbit/tome-blocks-core is bumped to release the layoutGrid platform primitives merged earlier but never published (the registry's 0.8.0 predates that merge): BlockMeta.nestable/minColSpan, withChildPlacement, the reserved _colSpan/_rowSpan/_order field constants, and blockRegistry.getNestableBlocks(). Without this, a consumer wiring the layoutGrid allowlist would call a getNestableBlocks that its installed blocks-core@0.8.0 does not have.

  Domain packs (lms, catalog, sc, org) are intentionally deferred — they compose into their own domain layouts and can opt in when a consumer needs them.

• Updated dependencies [c7d0afc]

  • @wabbit/tome-blocks-core@0.9.0
  • @wabbit/tome-blocks-extras@0.9.0

0.8.x

0.7.xMinor

• Expose a client-safe ./demo export (the already-built, payload-free getDemoProps module) on each block pack, separate from the payload-importing root barrel.

  The root barrel (.) eagerly pulls each block's config, which imports payload (→ richtext-lexical → pino → worker_threads). A consumer that registers packs client-side (the wabbit /blocks gallery storefront, B6) can't import getDemoProps from the root barrel without dragging payload/worker_threads into the browser bundle (build failure).

  The dist/demo.* module is already built and contains only demo-data + type imports — this change just makes it importable as @wabbit/tome-blocks-<pack>/demo.

  Additive; no code or runtime change to the packs.

  NOTE: this is the getDemoProps half of the client-safe gallery-registration fix. The companion piece — a client-safe block-meta/descriptor export (slug/label/variants/tier, separate from the payload-importing config the gallery bridges currently read .meta off) — is still needed before B6 can register packs entirely off the root barrel.

  Tracked separately.

• Expose a client-safe ./meta export on each block pack: payload-free block descriptor metadata (slug/name/description/category/tags/source + variants), separate from the payload-importing root barrel.

  This is the companion to the ./demo export. Each block's meta literal is now extracted into a co-located payload-free meta module that the block config imports, and a pack-level ./meta entry exposes the full descriptor list as <pack>BlockMeta.

  A consumer registering packs client-side (the wabbit /blocks gallery storefront, B6) can now read block metadata for gallery entries without importing the root barrel, which eagerly pulls each block's config (payload -> richtext-lexical -> pino -> worker_threads) into the browser bundle.

  Additive and behavior-preserving: defineBlock receives the same meta object (now imported rather than inline); the block registry, configs, demos, and existing exports are unchanged. The pack BlockMeta array is also re-exported from the root barrel for path-alias consumers.

• Updated dependencies [28802fa]

• Updated dependencies [66c611c]

• Updated dependencies [8958d41]

  • @wabbit/tome-blocks-extras@0.7.0
  • @wabbit/tome-blocks-core@0.7.0

0.6.x

0.5.xMinor

• Linked cohort version alignment (no functional change in this package).

0.4.x

0.3.xMinor

• Sprint 3 blocks split — v0.2.0

  Extracted the Tome blocks monolith (@wabbit/tome-blocks) into independently publishable bundle packages. Each bundle is independently installable, tree-shakeable, and testable in isolation.

  New packages (all v0.2.0):

  • @wabbit/tome-blocks-core — registries, defineBlock/defineBundle, variants, thumbnails, admin components (BlockPicker, VariantPicker)
  • @wabbit/tome-blocks-marketing-starter (free) — 8 marketing blocks: Hero, FeatureHero, CTA, LogoSlider, Pricing, Testimonial, FAQ, Banner
  • @wabbit/tome-blocks-content-writer (free) — 10 editorial blocks: Blog, Archive, PostHero, RelatedPosts, EditorialOpener, EditorialBridge, EditorialSidenote, EditorialFigure, EditorialColophon, EditorialFootnotes
  • @wabbit/tome-blocks-agency-essentials (starter) — 10 agency blocks: About, Contact/Form, Gallery, Media, SplitView, Stat, StatBar, TeamRoster, Timeline
  • @wabbit/tome-blocks-editorial-pack (pro) — 8 editorial blocks: DataHero, Feature, InfoPanel, MessagePanel, MetricStrip, SplitPanel, StatusBoard, TextReveal
  • @wabbit/tome-blocks-signal-theme (pro) — 33 Signal narrative blocks
  • @wabbit/tome-blocks-lms-pack (pro) — scaffold for LMS blocks (Wave 3)
  • @wabbit/tome-blocks-catalog-pack (pro) — scaffold for catalog/ecommerce blocks (Wave 3)
  • @wabbit/tome-blocks-sc-pack (niche) — scaffold for Star Citizen blocks (Wave 3)
  • @wabbit/tome-blocks-extras (pro) — 47 residual blocks (heroes, layout, content, marketing)

  @wabbit/tome-blocks is now a meta-package that re-exports all bundle packages and provides registerAll(blockRegistry, bundleRegistry) as a convenience function.

  Render colocation: All 113 render .tsx components migrated from the monolith into their owning bundle packages (./render subpath on each bundle).

  Breaking changes (internal):

  • @wabbit/tome-blocks/blocks and @wabbit/tome-blocks/bundles subpaths removed (were Sprint 2 shims)
  • packages/blocks/src/render/ category index files removed (replaced by per-bundle ./render subpaths)

  Migration:

  // Before (monolith singleton, all blocks loaded)
  import "@wabbit/tome-blocks";
  
  // After (explicit registration, tree-shakeable)
  import {
    blockRegistry,
    bundleRegistry,
  } from "@wabbit/tome-blocks-core/registry";
  import { register } from "@wabbit/tome-blocks-marketing-starter";
  register(blockRegistry, bundleRegistry);
  
  // Or use the meta-package convenience function
  import {
    blockRegistry,
    bundleRegistry,
    registerAll,
  } from "@wabbit/tome-blocks";
  registerAll(blockRegistry, bundleRegistry);

• Updated dependencies [f2202cd]

  • @wabbit/tome-blocks-core@0.3.0