Add a compileEdge parameter to compileOpenNextConfig

[vicb]

The cloudflare adapter will move away from using an internal middleware.

With this change we can still force the compilation of an edge configuration when the middleware is part of the server bundle.

(Longer term we might want to find a better solution to detect this)

[changeset-bot]

🦋 Changeset detected

Latest commit: 629fba6

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

This PR includes changesets to release 3 packages

Name	Type
@opennextjs/aws	Patch
app-pages-router	Patch
app-router	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

pnpm add https://pkg.pr.new/@opennextjs/aws@796

commit: 629fba6

[github-actions]

Coverage Report

Status	Category	Percentage	Covered / Total
🔵	Lines	26.22%	2358 / 8992
🔵	Statements	26.22%	2358 / 8992
🔵	Functions	52.71%	126 / 239
🔵	Branches	73.15%	586 / 801

File Coverage

File	Stmts	Branches	Functions	Lines	Uncovered Lines
Changed Files
packages/open-next/src/build.ts	0%	0%	0%	0%	1-83
packages/open-next/src/build/compileConfig.ts	0%	0%	0%	0%	1-122

Generated in workflow #1101 for commit 629fba6 by the Vitest Coverage Report Action

[conico974]

LGTM,
I think in the long term, we could look at the wrappers used to determine what we need to do here.

[vicb]

I think in the long term, we could look at the wrappers used to determine what we need to do here.

+1, the wrapper should have a way to indicate what they need.

Thanks for the review!