TypeScript Error: defineRouting expects 0 arguments but got 1 during npm run build

[NachoTamayo]

Description

I'm encountering a TypeScript error when running npm run build in my Next.js project that uses next-intl. Interestingly, the error does not occur when I run npm run dev; everything works as expected in the development environment.

Error Message:

./i18n/routing.ts:4:38
Type error: Expected 0 arguments, but got 1.

  2 | import { defineRouting } from "next-intl/routing";
  3 |
 >4 | export const routing = defineRouting({
    |                                      ^
  5 |   locales: ["en", "es"],
  6 |   defaultLocale: "en",
  7 |   pathnames: {

Verifications

• I've verified that the problem I'm experiencing isn't covered in the docs.
• I've searched for similar, existing issues on GitHub and Stack Overflow.
• I've compared my app to a working example to look for differences.

Mandatory reproduction URL

https://github.com/amannn/next-intl-bug-repro-app-router

Reproduction description

Steps to reproduce:

1. Set up a Next.js project with TypeScript and install next-intl.

2. Create an i18n/routing.ts file with the following content:

import { defineRouting } from "next-intl/routing";

export const routing = defineRouting({
  locales: ["en", "es"],
  defaultLocale: "en",
  pathnames: {
    // Custom route configurations
  },
});

3. Run npm run build to build the project for production.

Expected behaviour

The project should build successfully without any TypeScript errors, just as it does during development with npm run dev.

Actual Behavior:

The build process fails with the TypeScript error mentioned above, indicating that defineRouting expects 0 arguments but received 1.

Additional Information:

tsconfig.json:

{
  "compilerOptions": {
    "target": "es5",
    "lib": ["dom", "dom.iterable", "esnext"],
    "allowJs": true,
    "skipLibCheck": true,
    "strict": true,
    "forceConsistentCasingInFileNames": true,
    "noEmit": true,
    "esModuleInterop": true,
    "module": "esnext",
    "moduleResolution": "node",
    "resolveJsonModule": true,
    "isolatedModules": true,
    "jsx": "preserve",
    "incremental": true,
    "plugins": [{ "name": "next" }],
    "types": ["@testing-library/jest-dom", "jest", "node"],
    "paths": { "@/*": ["./*"] },
    "typeRoots": ["./types", "./node_modules/@types"]
  },
  "include": [
    "next-env.d.ts",
    "**/*.ts",
    "**/*.tsx",
    ".next/types/**/*.ts",
    "global.d.ts",
    "jest.config.js"
  ],
  "exclude": ["node_modules"]
}

[github-actions[bot]]

Thank you for your report!

Unfortunately, the reproduction is missing or incomplete, and as such we cannot investigate this issue. Please add a reproduction to the issue, otherwise it will be closed automatically.

Templates:

• App Router
• Pages Router

Creating a good bug report takes time.

To help us resolve the issue quickly, please simplify the reproduction as much as possible by removing any unnecessary code, files, and dependencies that are not directly related to the problem. The easier it is for us to see the issue, the faster we can help you.

Apart from the reproduction, make sure to include the precise steps on how to reproduce the issue, e.g.:

1. Open reproduction
2. Click on …
3. See error: …

Thank you for your understanding!

FAQ

"I've included a reproduction, what is missing?"

This comment might have been added because your reproduction doesn't point to a destination where the issue can be reproduced. Please make sure that the latest changes were saved in the reproduction and that the link is correct.

[NachoTamayo]

Hello, I can't include more about reproduction because it is very simple and it is al explained in the 1st post.

All that I can do is to share my project and you can try it yourself @amannn

https://github.com/NachoTamayo/VTTS/

Regards

[amannn]

If you can provide a minimal reproduction based on the provided template then I'm happy to have a look, but bug reports are not meant for general support requests—sorry.

I'll move this to a discussion.

[ddunlop]

Incase anyone stumbles on this - it's likely that the typescript version being used to build is outdated. Try updating your typescript dependency and see if this error disappears.

[maciejszubiczuk]

I have encountered the same issue and upgrading to the latest TypeScript version fixed the issue for me 👍