z4nr34l / next-easy-middlewares

Missing polyfill for multiple next.js middlewares
https://next-easy-middlewares.vercel.app/
MIT License
87 stars 4 forks source link

dont work i18n middleware #47

Closed godzzdeal closed 1 month ago

godzzdeal commented 1 month ago

I need help

Hi, im use NextJS 14 and TypeScript

when I do "export default" in "middleware.ts"

//middleware.ts

export default async function internationalized(request: NextRequest) {
  return intlMiddleware(request);
}

export const config = {
  matcher: ["/((?!api/|_next/|_static|_vercel|[\\w-]+\\.\\w+).*)"],
};

everything works perfectly, but when I use your library, it stops working. I start getting 404 all the time

//middleware.ts with next-easy-middlewares

const globalMiddlewares: Record<string, MiddlewareFunction> = {
  before: async (request: NextRequest) => {
    return intlMiddleware(request);
  },
};

const middlewares = {};

export const middleware: MiddlewareFunction = createMiddleware(
  middlewares,
  globalMiddlewares
);
//intlMiddleware.ts

import createMiddleware from "next-intl/middleware";
import { AppConfig } from "@/config/app.config";

export const intlMiddleware = createMiddleware({
  locales: AppConfig.locales,
  defaultLocale: AppConfig.defaultLocale,
  localeDetection: AppConfig.localeDetection,
  localePrefix: AppConfig.localePrefix,
});

maybe I'm using this tool incorrectly, but I've tried many ways.

linear[bot] commented 1 month ago

NEM-17 dont work i18n middleware

z4nr34l commented 1 month ago

Cloud you share your repository with me? If not I will need at least versions (from package.json) of:

z4nr34l commented 1 month ago

For 90% you fallen into global middleware redirect bug - which should be fixed in #49.

You can test it today using:

npm i next-easy-middlewares@beta