Build error when using standard next js alias

[mr-scrpt]

Description

Throughout the project I use the @ alias that next js provides, and it works in the development stage configuration as well

import { getRequestConfig } from "next-intl/server";
import { i18n, isValidLocale } from "./domain/type";
import { routing } from "./routing";

export default getRequestConfig(async ({ requestLocale }) => {
  let locale = await requestLocale;

  if (!locale || !isValidLocale(locale)) {
    locale = routing.defaultLocale;
  }

  return {
    locale,
    messages: (
      await import(`@/shared/dictionary/${i18n.dictionaryPath}/${locale}.json`)
    ).default,
  };
});

But as soon as I try to build the pnpm build project I get an error

   ▲ Next.js 15.1.5

   Creating an optimized production build ...
 ✓ Compiled successfully
 ✓ Linting and checking validity of types
 ✓ Collecting page data
Error occurred prerendering page "/en/contact". Read more: https://nextjs.org/docs/messages/prerender-error
Error: Cannot find module './dictionary/en.json'
    at /home/mr/Project/work/maksim/mz-partners/next/.next/server/chunks/912.js:1:115
    at async /home/mr/Project/work/maksim/mz-partners/next/.next/server/chunks/912.js:1:5031
    at async /home/mr/Project/work/maksim/mz-partners/next/.next/server/chunks/256.js:2:80931
    at async /home/mr/Project/work/maksim/mz-partners/next/.next/server/chunks/256.js:2:81683
    at async /home/mr/Project/work/maksim/mz-partners/next/.next/server/chunks/256.js:2:82025
    at async n (/home/mr/Project/work/maksim/mz-partners/next/.next/server/chunks/912.js:1:6108)
Export encountered an error on /[locale]/contact/page: /en/contact, exiting the build.
 ⨯ Static worker exited with code: 1 and signal: null
 ELIFECYCLE  Command failed with exit code 1.

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

On any project

Reproduction description

1. Install next
2. Install and configure next-intl

Expected behaviour

should work

[amannn]

Maybe this is a Next.js bug, dynamic imports is nothing that next-intl has any control over.

I've personally always used relative paths which work fine.