fix: bundle h3 and cookie-es into the server build

[brenelz]

Problem

Fixes #2101
Fixes #2178

@solidjs/start depends on h3 v2 (2.0.1-rc.16), but nitropack and unstorage depend on h3 v1. With yarn (both issue reporters used it), h3 v1 gets hoisted to the project root. Because the SSR build left h3 external, the emitted dist/server/entry-server.js contained a bare import { defineHandler, ... } from "h3", and when nitro's rollup bundled that file it resolved "h3" from the project root, hit v1, and failed with:

RollupError: entry-server.js: "defineHandler" is not exported by "node_modules/h3/dist/index.mjs"

cookie-es has the same v1/v2 split and is exposed to the same failure.

Fix

Add h3 and cookie-es to resolve.noExternal alongside @solidjs/start, so they are bundled into entry-server.js during the Vite SSR build. Since no bare h3/cookie-es import survives into the intermediate artifact, nitro can never re-resolve them against the wrong hoisted copy, regardless of package manager.

Verification

• Built the bare fixture: Vite client + SSR builds, nitro server build, and prerender all complete without errors.
• Inspected the built entry-server.js: the only remaining external imports are node:stream and solid-js/solid-js/web/solid-js/web/storage — no bare h3 or cookie-es imports remain, so the original resolution failure cannot occur.
• Smoke-tested the production output: node .output/server/index.mjs serves / with HTTP 200 and SSR-rendered content.

🤖 Generated with Claude Code

[netlify]

✅ Deploy Preview for solid-start-landing-page ready!

Name	Link
🔨 Latest commit	48a3657
🔍 Latest deploy log	https://app.netlify.com/projects/solid-start-landing-page/deploys/6a57fa8e4adf55000836dfa2
😎 Deploy Preview	https://deploy-preview-2183--solid-start-landing-page.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
🤖 Make changes	Run an agent on this branch

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 48a3657

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

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

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/solidjs/solid-start/@solidjs/start@2183

npm i https://pkg.pr.new/solidjs/solid-start/@solidjs/vite-plugin-nitro-2@2183

commit: 48a3657

[birkskyum]

Is it the Nitro v2 plugin that pollute with old h3 packages, or where are they imported form?

[brenelz]

Is it the Nitro v2 plugin that pollute with old h3 packages, or where are they imported form?

Yes. The Nitro v2 plugin introduces old H3 transitively:
@solidjs/vite-plugin-nitro-2
└─ nitropack@2.13.1
├─ h3@1.15.6
├─ listhen → h3@1.15.6
└─ unstorage@1.17.4 → h3@1.15.6
h3@1.15.6 then introduces cookie-es@1.2.2. Nitro itself also directly uses cookie-es@2.