Skip to content

Add a reference page for the @harperfast/vite plugin (and fix stale package name) #540

Description

@Ethan-Arrowood

Gap

There is no reference documentation for the Vite/React integration. The only mention in the entire docs build is a single bullet in reference/v5/components/overview.md (~line 135) that:

  1. has no config examples (no config.yaml, no output/ssr keys, no pairing-with-static contract), and
  2. uses the stale package name @harperfast/vite-plugin — renamed to @harperfast/vite in v1.0.0.

Impact

The @harperfast/skills rule serving-web-content cannot have its Vite/React half migrated to docs-generated (the static-files half already has good reference docs). Sourcing the current bullet as-is would also reintroduce the wrong package name. Part of the broader create-harper CLI docs cascade (see also creating-harper-apps).

Suggested fix

Add an atomic reference page for @harperfast/vite covering: the output/ssr config keys, pairing with the static plugin (shared output dir is the only contract), SPA vs SSR config.yaml, dev (harper dev, middleware-mode HMR) vs prod (harper runvite build) behavior, and the install command. Fix the stale package name in components/overview.md.

Filed while auditing rule/doc coverage for @harperfast/skills. sent with Claude Opus 4.8

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    content📝 Content specific issues and requests - text, examples, missing info, or clarity

    Type

    Fields

    Priority

    None yet

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions