How to have i18n.ts come along with the build?

[boris-arkenaar]

I'm trying out the translations server side. It works in development, but I'm running into an issue when built. The build runs fine, but when I run the app afterwards it exits with the message that it can't find 'i18n.ts'. What is the best approach to have this file come along in the build?

[agustif]

Make sure you add it to your tsconfig.json?

Where are you locating/importing it, what's the error message?

[boris-arkenaar]

I'm following the docs https://next-intl-docs.vercel.app/docs/getting-started/app-router-server-components#i18nts

Didn't think much of it, but when building and then launching I get the following in the console:

- ready started server on [::]:3000, url: http://localhost:3000
Error: Could not find i18n config at /app/i18n.ts, please provide a valid path.

Looking at the code in the docs again I see that i18n.ts is not explicitly imported but the path is just passed as a string to the next-intl/plugin function. So, i18n.ts needs to be copied to the resulting build verbatim. I explicitly copy this file now in my Dockerfile. (Running on Vercel works without any changes though.) Is that the correct approach, or am I missing something?

[boris-arkenaar]

I'm not importing the file, that's the thing. It goes like this: const withNextIntl = require('next-intl/plugin')('./i18n.ts');

[boris-arkenaar]

No idea if I can do something like

import i18n from './i18n';
const withNextIntl = require('next-intl/plugin')(i18n);

Can't find the source for this function in the repo.

[boris-arkenaar]

No, the function requires a string as input.

[amannn]

i18n.ts needs to be copied to the resulting build verbatim.

That's a great point, thanks for pointing this out @boris-arkenaar! We only need the i18n.ts file during next dev and next build, not during next start.

I've addressed this in d4eee0d, the next RSC beta release will no longer require the file to be present after the build.

[boris-arkenaar]

That's great to hear! Makes more sense.