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>
26 lines
655 B
TypeScript
26 lines
655 B
TypeScript
import { mergeAttributes, Node } from '@tiptap/core'
|
|
import Mention from '@tiptap/extension-mention'
|
|
|
|
export default Mention.extend({
|
|
renderHTML({ node, HTMLAttributes }) {
|
|
return [
|
|
'a',
|
|
mergeAttributes(
|
|
{
|
|
href: `https://gbf.wiki/${node.attrs.id.name.en}`,
|
|
target: '_blank',
|
|
},
|
|
{ 'data-type': this.name },
|
|
{ 'data-element': node.attrs.id.element.slug },
|
|
{ tabindex: -1 },
|
|
this.options.HTMLAttributes,
|
|
HTMLAttributes
|
|
),
|
|
this.options.renderLabel?.({
|
|
options: this.options,
|
|
node,
|
|
suggestion: null,
|
|
}) || '',
|
|
]
|
|
},
|
|
})
|