hensei-web/i18n/routing.ts
Justin Edmund e132d31b57 Fix Railway deployment and TypeScript errors
- 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>
2025-09-04 01:44:37 -07:00

8 lines
No EOL
239 B
TypeScript

import {defineRouting} from 'next-intl/routing'
import {locales, defaultLocale} from '../i18n.config'
export const routing = defineRouting({
locales,
defaultLocale,
localePrefix: 'as-needed' // Show locale in URL when not default
})