Justin Edmund
e132d31b57
- Add next-intl routing configuration using defineRouting
- Update navigation and middleware to use new routing config
- Fix all TypeScript errors in components
- Add Node.js 20 configuration for Railway (.nvmrc and .mise.toml)
- Add patch script for next-intl ESM compatibility
- Fix nullable types and missing props across components
- Update package.json engines to specify Node.js 20.x
This fixes the deployment failure on Railway by:
1. Resolving all TypeScript compilation errors
2. Working around Node.js ESM module resolution issues with next-intl
3. Specifying Node.js 20 for consistent builds
🤖 Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>
20 lines
901 B
TypeScript
20 lines
901 B
TypeScript
import {getRequestConfig} from 'next-intl/server'
|
|
import {routing} from './routing'
|
|
import {type Locale} from '../i18n.config'
|
|
|
|
// next-intl v4: global request config used by getMessages()
|
|
export default getRequestConfig(async ({requestLocale}) => {
|
|
let locale = (await requestLocale) as Locale | null;
|
|
if (!locale || !routing.locales.includes(locale)) {
|
|
locale = routing.defaultLocale;
|
|
}
|
|
|
|
// Load only i18n namespaces; exclude content data with dotted keys
|
|
const common = (await import(`../public/locales/${locale}/common.json`)).default;
|
|
const about = (await import(`../public/locales/${locale}/about.json`)).default;
|
|
// Re-include updates.json now that dotted version keys have been renamed (e.g., v1_2_1)
|
|
const updates = (await import(`../public/locales/${locale}/updates.json`)).default;
|
|
const messages = {common, about, updates} as const;
|
|
|
|
return {locale, messages};
|
|
});
|