Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / hoangvvo/next-connect issues and pull requests

#247 - TypeScript fails when exporting a Router object

Issue - State: open - Opened by ayortanli 3 months ago

#245 - Add Next.js 14 Example with Implementation of next-connect

Issue - State: closed - Opened by zehan12 12 months ago - 2 comments

#244 - How to implement passport with next-connect in Next 14?

Issue - State: open - Opened by RicardoNRevs 12 months ago - 1 comment

#243 - docs: update router return statement to include type casting for next 14 app router

Pull Request - State: open - Opened by OgDev-01 about 1 year ago - 3 comments

#242 - fetch remote image with cors

Issue - State: open - Opened by janwagner about 1 year ago

#241 - App/Route issue "Promise<unknown>"

Issue - State: open - Opened by albertpeiro about 1 year ago - 5 comments

#239 - nextjs14 with next-connect not working

Issue - State: open - Opened by epubreader about 1 year ago - 1 comment

#237 - Not able to use multer as middleware

Issue - State: open - Opened by ABHI190701 over 1 year ago

#236 - Incorrect issue report

Issue - State: open - Opened by nordicgit70 over 1 year ago

#235 - Defining custom properties/types per handler in v1?

Issue - State: open - Opened by codsane over 1 year ago - 1 comment

#234 - Next Js App router catch-all error handler

Issue - State: open - Opened by thomasheimh over 1 year ago - 4 comments

#233 - Fixes path for example Next.js App Router API endpoint

Pull Request - State: closed - Opened by mscottford over 1 year ago - 1 comment

#232 - feat: add handleNextRequest utility to run express app in next app route

Pull Request - State: open - Opened by thgh over 1 year ago - 1 comment

#231 - Next connect with multer

Issue - State: open - Opened by WZoptal over 1 year ago - 1 comment

#230 - What is "RequestContext" and how it should be used when using NextJs 13?

Issue - State: open - Opened by hywook4 over 1 year ago - 2 comments

#229 - How to use next-connect with nextjs 13 App router and passport?

Issue - State: open - Opened by blueyestar over 1 year ago - 1 comment

#227 - Nextjs routes

Issue - State: open - Opened by majeed4u over 1 year ago - 2 comments

#226 - OPTIONS

Issue - State: open - Opened by HighError almost 2 years ago

#225 - Migration guide from 0.13.0?

Issue - State: open - Opened by yeikel almost 2 years ago - 3 comments

#224 - Is this project alive?

Issue - State: open - Opened by Toshimichi0915 almost 2 years ago - 5 comments

#223 - how to use in next13 ?

Issue - State: closed - Opened by Scorpio-nan almost 2 years ago - 2 comments

#222 - types are incorrect on cloned router

Issue - State: closed - Opened by mattpodolak almost 2 years ago - 1 comment

#221 - docs(readme): Make middleware example runnable

Pull Request - State: closed - Opened by damassi almost 2 years ago - 2 comments

#220 - Are there plans to support the new Route Handlers API?

Issue - State: open - Opened by jmikrut almost 2 years ago - 14 comments

#219 - How can I handle same method twice?

Issue - State: open - Opened by GHCMelo about 2 years ago - 3 comments

#218 - Bump json5 from 2.2.1 to 2.2.3

Pull Request - State: open - Opened by dependabot[bot] about 2 years ago - 2 comments
Labels: dependencies

#217 - Issues making multer file optional

Issue - State: closed - Opened by GodsonAddy about 2 years ago - 1 comment

#216 - Type error: try to use multer with next connect

Issue - State: closed - Opened by DarlonHenrique about 2 years ago - 2 comments

#215 - Remove necessity for next to always be defined when using .run

Pull Request - State: open - Opened by sf185127 over 2 years ago - 2 comments

#213 - unexpectedly enters the If statement in a middleware and sends error

Issue - State: closed - Opened by perinazzoo over 2 years ago - 1 comment

#212 - default value of options.onError

Issue - State: open - Opened by thilllon over 2 years ago - 1 comment

#211 - [V1] global catch-all success route

Issue - State: closed - Opened by raphaelbadia over 2 years ago - 2 comments

#210 - expressWrapper is not full-supported

Issue - State: open - Opened by yunsii over 2 years ago - 3 comments
Labels: bug

#208 - feat: add expressWrapper util

Pull Request - State: closed - Opened by hoangvvo over 2 years ago - 2 comments

#207 - router class rearchitecture

Pull Request - State: closed - Opened by hoangvvo over 2 years ago - 2 comments

#206 - .clone() returns a new instance but can not produce .handler()

Issue - State: closed - Opened by BounSweFerhatSal over 2 years ago - 2 comments

#205 - Can not catch error when using async and await

Issue - State: closed - Opened by sendking over 2 years ago - 6 comments

#204 - types error after updating to v1.0.0-next.2

Issue - State: closed - Opened by HT-Moh over 2 years ago - 1 comment

#203 - Can next-connect run on Nextjs middleware?

Issue - State: closed - Opened by gyto over 2 years ago - 3 comments

#202 - Possible to catch missing `export default router.handler()`

Issue - State: open - Opened by larsqa over 2 years ago - 2 comments

#201 - How to set errorHandler globally in v1?

Issue - State: open - Opened by larsqa over 2 years ago - 9 comments

#200 - Edge Runtime Router

Pull Request - State: closed - Opened by hoangvvo over 2 years ago - 2 comments
Labels: feature

#199 - Add benchmark and update readme

Pull Request - State: closed - Opened by hoangvvo over 2 years ago - 2 comments

#198 - Always attach req.params

Pull Request - State: closed - Opened by hoangvvo over 2 years ago - 2 comments

#197 - security: always return generic 500 error

Pull Request - State: closed - Opened by hoangvvo over 2 years ago - 2 comments

#196 - V1 Rewrite

Pull Request - State: closed - Opened by hoangvvo over 2 years ago - 5 comments

#194 - redirecting in getServerSideProps middleware

Issue - State: closed - Opened by raphaelbadia over 2 years ago - 3 comments

#192 - incorrect baseurl in getStaticProps + axios(get)

Issue - State: open - Opened by jagnani73 over 2 years ago - 1 comment

#191 - param onMatch() not working

Issue - State: closed - Opened by jamesmogambi over 2 years ago - 1 comment

#190 - Build module using rollup

Pull Request - State: closed - Opened by hoangvvo over 2 years ago - 2 comments

#189 - Cannot access '__WEBPACK_DEFAULT_EXPORT__' before initialization

Issue - State: closed - Opened by brianlovin almost 3 years ago - 5 comments

#188 - how to order the response [onNoMatch]

Issue - State: closed - Opened by a7medmo7med9 almost 3 years ago - 2 comments

#187 - docs: fix Common errors example comment

Pull Request - State: closed - Opened by manak1 almost 3 years ago - 3 comments

#186 - hiding error stacktrace

Issue - State: closed - Opened by ghost almost 3 years ago - 1 comment

#185 - Handler not getting triggered on redirect.

Issue - State: open - Opened by Goutam192002 almost 3 years ago - 1 comment

#184 - Handle error in getServerSideProps

Issue - State: closed - Opened by nemanjam almost 3 years ago - 1 comment

#183 - How to use different middlewares for each method on the same handler

Issue - State: closed - Opened by RadoslavMarinov almost 3 years ago - 1 comment

#182 - TypeScript - NextConnect not compatible with NextApiHandler

Issue - State: closed - Opened by osdiab almost 3 years ago - 2 comments

#181 - Same API handler called when reload

Issue - State: closed - Opened by develoQ almost 3 years ago - 2 comments

#180 - ErrorHandler type miss `next` type

Issue - State: closed - Opened by 22mahmoud almost 3 years ago - 1 comment

#179 - `handler()` does not always resolve, causing memory leak

Issue - State: closed - Opened by hoangvvo about 3 years ago

#178 - fix: make sure handler is resolvable

Pull Request - State: closed - Opened by hoangvvo about 3 years ago - 12 comments

#177 - Export types `NextHandler`, `Middleware`, `RequestHandler`, `ErrorHandler`

Issue - State: closed - Opened by JasonMore about 3 years ago - 1 comment

#176 - typescript: added export for types

Pull Request - State: closed - Opened by JasonMore about 3 years ago - 3 comments

#174 - fix onNoMatch problematic example

Pull Request - State: closed - Opened by lamualfa about 3 years ago - 2 comments

#173 - Running custom handler from GraphQL

Issue - State: closed - Opened by gyto about 3 years ago - 2 comments

#172 - Consider changing the way how request and response can be extended

Issue - State: closed - Opened by Alannek1992 about 3 years ago - 1 comment

#171 - Improve NextConnect method Types

Pull Request - State: closed - Opened by saucesteals about 3 years ago - 7 comments

#170 - Running a handler at the end of chain?

Issue - State: closed - Opened by younanjo about 3 years ago - 4 comments

#169 - How can I access raw request body?

Issue - State: closed - Opened by lumenwrites about 3 years ago - 2 comments

#168 - How can I set cookies on the response, and then redirect?

Issue - State: closed - Opened by lumenwrites about 3 years ago - 1 comment

#167 - Cookies not present when redirected with form_post

Issue - State: closed - Opened by agustingabiola about 3 years ago - 2 comments

#166 - Complete handler chain if res is sent

Pull Request - State: closed - Opened by jakeorr about 3 years ago - 15 comments

#165 - Socket IO

Issue - State: closed - Opened by kotsh23 about 3 years ago - 1 comment

#164 - Promise does not resolve is error occurs in the middle of the handler chain

Issue - State: closed - Opened by pluby about 3 years ago - 3 comments

#163 - Yarn berry PnP + Next.js 12 has import error.

Issue - State: closed - Opened by minkichoe over 3 years ago - 10 comments

#162 - fix(#161): use() accepts array

Pull Request - State: open - Opened by jimisaacs over 3 years ago - 11 comments

#161 - Possible regression away from express API

Issue - State: open - Opened by jimisaacs over 3 years ago

#160 - Detect that route exists, but method not allowed

Issue - State: open - Opened by 1aerostorm over 3 years ago - 6 comments

#159 - 404 error when using async functions

Issue - State: open - Opened by bramvbilsen over 3 years ago - 13 comments

#158 - Right way to use instance of next-connect?

Issue - State: closed - Opened by IRediTOTO over 3 years ago - 1 comment

#157 - Allow regular expressions to be used for route.

Pull Request - State: closed - Opened by mmillies over 3 years ago - 8 comments

#156 - use() routes with RegExps should work.

Issue - State: closed - Opened by mmillies over 3 years ago

#155 - graphql-shield

Issue - State: closed - Opened by Manubi over 3 years ago - 2 comments

#153 - TypeScript: Body prop doesn't extend

Issue - State: closed - Opened by Nautman over 3 years ago - 2 comments

#152 - Export the options interface

Pull Request - State: closed - Opened by smitssjors over 3 years ago - 4 comments

#151 - Nextjs jwt.getToken and getSession returning null with next-connect handler

Issue - State: closed - Opened by mohsenmahoski over 3 years ago - 2 comments

#150 - NextJS API route with multiple middlewares

Issue - State: closed - Opened by mikeharrison4 over 3 years ago - 3 comments

#149 - next-connect doesn't work in production environment

Issue - State: closed - Opened by yuvaraj-anbarasan over 3 years ago - 5 comments

#148 - Async middleware

Pull Request - State: open - Opened by UncleClapton over 3 years ago - 3 comments