refactor: avoid nested h3 defineHandler call in createBaseHandler

[katywings]

What is the current behavior?

To decorate the handler and all middleware with FetchEvent, h3's defineHandler is wrapped in another defineHandler. This is not conforming with h3's intended API usage.

What is the new behavior?

Instead the handler and each middleware are decorated separately. This shouldn't change any behavior, but follows h3's usage patterns closer and hopefully reduces the chance of future related bugs.

More info

The old code was introduced during the devinxi work.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 95c6d24

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

[netlify]

❌ Deploy Preview for solid-start-landing-page failed. Why did it fail? →

Name	Link
🔨 Latest commit	95c6d24
🔍 Latest deploy log	https://app.netlify.com/projects/solid-start-landing-page/deploys/691cb47f4614490007d4c9f8

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@solidjs/start@2006

commit: 95c6d24

[brenelz]

Seems like a good change to me