@inkandswitch/patchwork-providers@0.5.1

Patch Changes

• 6f4f62f: Depend on solid-automerge instead of @automerge/automerge-repo-solid-primitives. The Solid bindings are published under the new name; the peer dependency of @inkandswitch/patchwork-providers-solid moves to solid-automerge (^2.0.1). Install solid-automerge in place of @automerge/automerge-repo-solid-primitives — the exported API (useDocument, createDocumentProjection, autoproduce, …) is unchanged.

@inkandswitch/patchwork-providers-solid@0.2.7

Patch Changes

• 6f4f62f: Depend on solid-automerge instead of @automerge/automerge-repo-solid-primitives. The Solid bindings are published under the new name; the peer dependency of @inkandswitch/patchwork-providers-solid moves to solid-automerge (^2.0.1). Install solid-automerge in place of @automerge/automerge-repo-solid-primitives — the exported API (useDocument, createDocumentProjection, autoproduce, …) is unchanged.
• Updated dependencies [6f4f62f]
  • @inkandswitch/patchwork-providers@0.5.1

@inkandswitch/patchwork@0.7.3

Patch Changes

• 8742cd2: Expose the individual vite plugins that patchwork() composes. Each one now has its own subpath — @inkandswitch/patchwork/vite/importmap, /vite/service-worker, /vite/config, /vite/dev, /vite/icons, /vite/html, /vite/manifest, /vite/netlify, /vite/static, /vite/build-info — and they are also re-exported from @inkandswitch/patchwork/vite as importmap, serviceworker, config, dev, icons, html, manifest, netlify, statics and buildInfo, so a site that wants its own composition can pick the pieces it needs instead of the whole default plugin array.
• Updated dependencies [94f6299]
• Updated dependencies [a96f250]
  • @inkandswitch/patchwork-elements@6.0.1
  • @inkandswitch/patchwork-plugins@1.2.1
  • @inkandswitch/patchwork-filesystem@0.2.6

@inkandswitch/patchwork-plugins@1.2.2

Patch Changes

• 3e67841: Omit suggestedImportUrl and frozenImportUrl from a new doc's @patchwork metadata when there is no value for them, instead of writing undefined.
• 3e67841: Split the datatype's import URL when creating a doc: @patchwork.suggestedImportUrl now holds the URL with the heads stripped, and @patchwork.frozenImportUrl holds the full URL including heads. getFrozenImportUrl reads the latter. URLs without heads are unchanged and set no frozenImportUrl.

@inkandswitch/patchwork-plugins@1.2.1

Patch Changes

• a96f250: Store the datatype's import URL without heads in @patchwork.suggestedImportUrl, and record the heads separately in @patchwork.suggestedImportUrlHeads. A doc created from a package pinned to specific heads now suggests the package itself, with the pin kept alongside it.

@inkandswitch/patchwork-filesystem@0.2.7

Patch Changes

• 3e67841: Split the datatype's import URL when creating a doc: @patchwork.suggestedImportUrl now holds the URL with the heads stripped, and @patchwork.frozenImportUrl holds the full URL including heads. getFrozenImportUrl reads the latter. URLs without heads are unchanged and set no frozenImportUrl.

@inkandswitch/patchwork-filesystem@0.2.6

Patch Changes

• a96f250: Store the datatype's import URL without heads in @patchwork.suggestedImportUrl, and record the heads separately in @patchwork.suggestedImportUrlHeads. A doc created from a package pinned to specific heads now suggests the package itself, with the pin kept alongside it.

@inkandswitch/patchwork-elements@6.0.1

Patch Changes

• 94f6299: <patchwork-view> no longer imports a document's suggestedImportUrl on its own. When no tool supports the document but the document names a suggested import, the view says so — "No tool was found for this document, but it suggests a package at …" — and offers a "⚡ Load suggested package" button. Clicking it raises a window.confirm naming the URL whose JavaScript is about to run; nothing is fetched until that's accepted. When a wildcard fallback tool is already mounted, the same offer arrives as a toast instead of replacing it, dismissable with its × or Escape.

@inkandswitch/patchwork@0.7.2

Patch Changes

• e1374ad: Serve the /packages/… builtin URLs in dev. Import maps don't apply to worker
  scripts, so code that starts one — @automerge/automerge-repo's shared
  subduction websocket worker, for instance — asks for the /packages/… path the
  build emits. Nothing served those in dev, and the worker failed to fetch; the
  dev server now redirects them to the same optimized dep the page's import map
  points at.
• e1374ad: Say what's actually wrong when a static package declares a directory that
  isn't there. The package resolved fine — its "patchwork": {"static": …} field
  is what's wrong — and "static source not found" named neither the field nor the
  path it pointed at. The error now quotes the declaration, gives the full path
  that's missing, and says that a package publishing its static tree as the root
  of its own tarball shouldn't set the field at all.

@inkandswitch/patchwork@0.7.1

Patch Changes

• 8b9206d: Don't copy static sources or write build-info.json when a dev server shuts
  down. closeBundle runs then too, so stopping vite was filling dist/ with
  a copy of every static source.