refactor: rename Start mode to app mode

[birkskyum]

Summary

• Renames the plugin-managed start option to app
• Renames StartOptions to AppOptions
• Uses app.root for the root component
• Groups explicit rendering entries under app.entries.client and app.entries.server
• Renames errorBoundary to productionErrorBoundary
• Moves typed env configuration from app.env to the top-level env option
• Updates internal plugin names, documentation, and example directories
• Keeps serverFunctions top-level

Why

app describes the optional layer where the plugin owns entries, rendering, dev serving, and build orchestration. It avoids tying that capability to the retired SolidStart name.

env and serverFunctions remain independent capabilities. They can be used by router integrations, manual SSR setups, and other projects without plugin-managed application rendering.

JavaScript configs using start or app.env receive migration errors. No compatibility aliases are retained before the stable release.

Testing

• pnpm run build
• pnpm run check
• app client suite: 46/46
• env suite: 48/48
• app SSR suite: 366/366
• HTTP bridge suite: 10/10

[changeset-bot]

🦋 Changeset detected

Latest commit: 88e2de8

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@solidjs/vite-plugin	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@solidjs/vite-plugin@327

commit: 88e2de8

[brenelz]

I think it was intentional to use the start name

[birkskyum]

I think it was intentional to use the start name

I understand that start was intentional. My concern is that it is not very descriptive as a configuration category. app groups the settings where the plugin manages the application lifecycle, including entries, document rendering, dev serving, and builds. serverFunctions remains separate because it does not require plugin-managed rendering.

If preserving the Start branding is important, that is a separate consideration (seems like we're beyond it), but I think app communicates the API boundary more clearly.