Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add additional metadata to RoutingResult #673

Merged
merged 8 commits into from
Dec 17, 2024

Conversation

conico974
Copy link
Contributor

This PR will help #665.
This may also allow us in the future to use https://github.com/vercel/next.js/blob/4d1613d049037b2b39295a9479c9f8c9a12df907/packages/next/src/server/base-server.ts#L1581 instead of getRequestHandler

Copy link

changeset-bot bot commented Dec 11, 2024

🦋 Changeset detected

Latest commit: 0be8461

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

Copy link

pkg-pr-new bot commented Dec 11, 2024

Open in Stackblitz

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

commit: 0be8461

@@ -31,3 +31,4 @@ export const AppPathsManifestKeys =
/* @__PURE__ */ loadAppPathsManifestKeys(NEXT_DIR);
export const MiddlewareManifest =
/* @__PURE__ */ loadMiddlewareManifest(NEXT_DIR);
export const AppPathsManifest = loadAppPathsManifest(NEXT_DIR);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need /* @__PURE__ */ here?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Probably not for all of them, but this is necessary for some part. Without it esbuild fail to remove some of the unused one and it can cause error at runtime

Copy link
Contributor

@vicb vicb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, only a few minor comments

@conico974
Copy link
Contributor Author

@vicb Sorry i think we need to change a few things in this PR actually.
This issue #677 made me think that we could have more than one resolved route.
I'll change this, add some unit test, and add the change you requested as well

@conico974 conico974 requested a review from vicb December 17, 2024 12:48
Copy link
Contributor

@vicb vicb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for adding tests!

I added only minor nits.

Copy link
Contributor

@vicb vicb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for all the update!

@@ -0,0 +1,8 @@
---
"@opennextjs/aws": patch
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe this should be minor (new feature) instead of patch (bug fix) ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it's ok this way, technically there is no new feature here, and it should have no impact at all for end user (even people with custom overrides)
Other PR that will depend on this one will be minor like #665

@conico974 conico974 merged commit 7140ca5 into opennextjs:main Dec 17, 2024
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants