Yongwoo Jung

This library is dependent on Next.js. Therefore, unless Next.js supports WebSocket communication methods, we cannot implement WebSocket communication.

Hi @stephane-segning Thanks for your PR Could you please check issue #17? (If you move the `@types/http-proxy`dependency to the devDependencies field, the TS compiler will not properly interpret the `NextHttpProxyMiddlewareOptions`...

Hi @stephane-segning I'm sorry but I don't quite understand. Can you explain what part is the problem and what solved it? If the user installs the `next-http-proxy-middleware` library, the `@types/http-proxy`...

> The problem is the TS config. I've updated it quite a little bit. And also, you should include all `*.d.ts` files inside the final release of your app. >...

> The problem is the TS config. I've updated it quite a little bit. And also, you should include all *.d.ts files inside the final release of your app. If...

Hi @wangwailok I'm checked a little while ago, and this llibrary is still working well, Could you please share with me the versions of the library you are using and...

It seems difficult to see this library as a kind of 'middleware' that is currently called by Next.js. This library has been used since Next.js v9, and at that time,...

@wangwailok In your case, it seems like you should use `NextApiRequest` and `NextApiResponse`. 😅 Because, this library is a middleware(handler) for handling API requests, and `NextRequest` and `NextResponse` are middlewares(handlers)...

Hi, @pluce Please return the result of executing the `httpProxyMiddleware` function. ```ts // e.g., ... export async function POS(...) { return httpProxyMiddleware(... {}); //

Hi, @stoompa Could you please share the your project repository?