Version Packages

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@pmndrs/docs@4.0.0

Major Changes

• #577 3e23829 Thanks @abernier! - Drop Docker. npx @pmndrs/docs build does the same build, so the image, the Dockerfile and
  the publish steps that maintained them are gone. ghcr.io/pmndrs/docs stops being pushed —
  its existing tags stay in the registry, frozen.

  Major because of the git tag, not the inputs: releases force-move vX, so anything short of a
  major would slide every caller pinning build.yml@v3 onto the Docker-free workflow. @v3
  keeps building through the image until its repository moves to @v4.

  build.yml itself keeps every input, every environment variable and the same Pages artifact.
  Only the build step changes, and docker_tag gives way to version — an npm version or range.

  The job keeps id-token: write — no longer to attest a Docker image, now to sign the npm
  publish with trusted publishing.

  preview.sh builds through the CLI too, and reads its options straight from the environment
  rather than forwarding each one into a container.

Minor Changes

• #574 e70f51e Thanks @abernier! - Publish the generator to npm, as npx @pmndrs/docs build.

  --format website statically exports the documentation site.
  --format fragment — the default — compiles MDX to plain HTML with no layout, stylesheet or
  script, either from a folder or from stdin, and needs nothing but node.

  bin/build.mjs is gone: it was never published, and built a server bundle rather than a
  static export.

Patch Changes

• #575 4a68fbd Thanks @abernier! - Stop repeating the Sandpack stylesheet on every streamed chunk

  useServerInsertedHTML is called back on each flush of the response and expects what is new
  since the last one, but the callback returned the whole Sandpack stylesheet every time. Pages
  carried one full copy per chunk — 145 identical copies of the same 8.9 kB on the worst of
  them, three quarters of the page weight.

  Which pages were hit moved from build to build: the stylesheet is a module-level singleton,
  so it depended on whether a page using Sandpack had been rendered earlier in the same build
  process. Pages with no Sandpack of their own paid for their neighbours.