feat: next.js support - #18
Merged
Merged
Conversation
zoedsoupe
marked this pull request as draft
September 22, 2025 20:14
added 2 commits
September 22, 2025 17:16
zoedsoupe
marked this pull request as ready for review
September 22, 2025 21:41
zoedsoupe
force-pushed
the
feat/next-support
branch
from
September 22, 2025 21:44
937ca44 to
ac90bcb
Compare
josevalim
reviewed
Sep 23, 2025
josevalim
reviewed
Sep 23, 2025
added 3 commits
September 30, 2025 16:01
Signed-off-by: zoey <zoey.spessanha@dashbit.co>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
this pr aims to implement next.js handlers for api routes
pages/api/**app router(edge api) andmidleware.tshandlers may be implemented too but isnt the focus right now.currently i'm having a module resolution failure with next.js webpack...solved