precompile feedback

[amannn]

Please use this thread to share feedback related to ahead-of-time compilation of messages.

Template for bug reports: https://github.com/amannn/nextjs-test-precompile

[keyboy21]

I tested precompile feature, it works well! Overall js bundle size is decreased about 9-15kbs depending on page. Interesting that precompilation finds invalid keys in translations.

[amannn]

Nice, that sounds great! And yes, invalid messages that would otherwise be detected during render are now already discovered during compilation.

[keyboy21]

During testing, I encountered the following error when trying to use a translation string with a variable. On dev mode

My messages file:

"HomePage": {
		"header": {
			"balance": "Баланс: {balance} сум",
			"topUpBalance": "Пополнить"
		},
	},

Usage in code:

<span className="px-4">
 {t("header.balance", {balance: toMoney(userInfo.data.data.balance)})}
</span>

Error message:

INVALID_MESSAGE: Message at `HomePage.header.balance` resolved to an array, but only strings are supported. See https://next-intl.dev/docs/usage/translations#arrays-of-messages

[keyboy21]

I'm on Windows, is this matter ?

[keyboy21]

browser logs

installHook.js:1  Server  Error: INVALID_MESSAGE: Message at `HomePage.header.balance` resolved to an array, but only strings are supported. See https://next-intl.dev/docs/usage/translations#arrays-of-messages
    at HeaderBalance (header-balance.tsx:9:10)
    at resolveErrorDev (react-server-dom-turbopack-client.browser.development.js:3197:48)
    at getOutlinedModel (react-server-dom-turbopack-client.browser.development.js:2432:22)
    at parseModelString (react-server-dom-turbopack-client.browser.development.js:2632:15)
    at Object.<anonymous> (react-server-dom-turbopack-client.browser.development.js:4554:20)
    at JSON.parse (<anonymous>)
    at initializeModelChunk (react-server-dom-turbopack-client.browser.development.js:1828:26)
    at getOutlinedModel (react-server-dom-turbopack-client.browser.development.js:2337:11)
    at parseModelString (react-server-dom-turbopack-client.browser.development.js:2729:15)
    at Array.<anonymous> (react-server-dom-turbopack-client.browser.development.js:4554:20)
    at JSON.parse (<anonymous>)
    at initializeModelChunk (react-server-dom-turbopack-client.browser.development.js:1828:26)
    at resolveConsoleEntry (react-server-dom-turbopack-client.browser.development.js:3488:13)
    at processFullStringRow (react-server-dom-turbopack-client.browser.development.js:4404:11)
    at processFullBinaryRow (react-server-dom-turbopack-client.browser.development.js:4300:7)
    at processBinaryChunk (react-server-dom-turbopack-client.browser.development.js:4523:19)
    at progress (react-server-dom-turbopack-client.browser.development.js:4799:9)
overrideMethod @ installHook.js:1
forward-logs-shared.ts:95 [HMR] connected

[keyboy21]

pnpm build works me too, but on dev error

[amannn]

Thanks, I've got a reproduction now and found the issue! Should have a fix out soon, I'll keep you posted.

[amannn]

@keyboy21 Fixed in next-intl@4.8.1, thanks for the report!

[creage]

Upgrading to v4.8.1 breaks our builds (Windows) with error

 NX   Failed to process project graph.

An error occurred while processing files for the @nx/next/plugin plugin
.
  - apps/client/next.config.ts:
[next-intl] Could not locate request configuration module.

This path is supported by default: ./(src/)i18n/request.{js,jsx,ts,tsx}

Alternatively, you can specify a custom location in your Next.js config:

const withNextIntl = createNextIntlPlugin(

Alternatively, you can specify a custom location in your Next.js config:

const withNextIntl = createNextIntlPlugin(
  './path/to/i18n/request.tsx'
);

Providing the path manually still doesn't help:

 NX   Failed to process project graph.

An error occurred while processing files for the @nx/next/plugin plugin
.
  - apps/client/next.config.ts: 
[next-intl] Could not find i18n config at ./src/i18n/request.ts, please provide a valid path.

[creage]

Yeah, we changed nothing, just bumped the version from 4.7.0 to 4.8.1

[amannn]

Uh, sorry about that! I'll look into it and get back to you. Thanks for the report!

[amannn]

@creage I tried to set up a failing repro here: https://github.com/amannn/next-intl-nx-test (uses windows-latest runner).

So far everything seems to pass with a very simple setup, but I might be missing something. Can you fork the repro and make edits based on your use case to have it fail and demonstrate the behavior you're seeing?

[creage]

@amannn Adding @nx/next/plugin configuration to your nx.json breaks the build.

But you need to clear your .nx folder before build, as it caches workspace.

[amannn]

Fixed in next-intl@4.8.2 (will be released in a bit)

[keyboy21]

Failed to run dev with bun

OS: Widows
bun v1.3.8 (with bun --bun next dev)
next-intl v4.8.2 with precompile enabled

⨯ Failed to load next.config.mjs, see more info here https://nextjs.org/docs/messages/next-config-error
error: Cannot find module 'use-intl/format-message/format-only' from ''

error: "next.cmd" exited with code 1
error: script "dev" exited with code 1

[keyboy21]

Error occures when using next config .mjs

[keyboy21]

It works on my local machine, sorry my bad, it's cashe from pnpm

[amannn]

Ok, let me know in case you have a reproduction that demonstrates an issue—I'll be sure to have a look.

[keyboy21]

@amannn It seems I didn't explain myself correctly, there was no issue. Everything works great!

[amannn]

Oh ok that's great to hear, thanks!

[jorrit]

The precompilation flag breaks placeholders and plurality rules in my app. Does it matter whether I use turbopack or webpack? My site (with Nextjs 15) only builds using webpack.

[amannn]

Any chance you can provide a reproduction based on https://github.com/amannn/nextjs-test-precompile? The features you mention should surely be supported.