Basic Usage
Default link text
Custom link text
Properties
API reference ID:
PackageName.ClassName.MemberNameExamples: mint-tsdocs.MarkdownDocumenter, mint-tsdocs.loadConfig, mint-tsdocs.CacheManager.typeAnalysisLink text. Defaults to the API item name if omitted.
Type Safety
RefLink validates links in two ways: Compile-time - TypeScript checks againstValidRefs.d.ts:
ValidRefs Set and applies styling:
Valid vs broken links
- Red color (#ef4444)
- Red dotted underline (2px)
- Red wavy text decoration
- Tooltip showing the error
Examples
Linking to different API items
RefId Format
API reference IDs follow:PackageName.ClassName.MemberName
Examples:
- Class:
mint-tsdocs.MarkdownDocumenter - Method:
mint-tsdocs.MarkdownDocumenter.generateFiles - Interface property:
mint-tsdocs.MintlifyTsDocsConfig.entryPoint
mint-tsdocs.MarkdownDocumenter → /reference/mint-tsdocs/MarkdownDocumenter
Fixing Broken Links
Links break when API items are renamed, deleted, or not exported.- Check TypeScript error in IDE
- Verify item exists in API reference navigation
- Update target to correct RefId
- Run
mint-tsdocs generateif source changed
Best Practices
Use RefLink for API references, PageLink for guides/concepts
Keep link text concise
Let TypeScript autocomplete guide you
Fix broken links before committing
Troubleshooting
Component not found
Component not found
Run
mint-tsdocs generate to copy components to docs/snippets/tsdocs/All links broken
All links broken
- Check
ValidRefs.jsxexists indocs/snippets/tsdocs/ - Run
mint-tsdocs generate - Refresh browser
No IDE autocomplete
No IDE autocomplete
Due to an MDX extension bug, try:
- Use relative path while editing:
"../snippets/tsdocs/RefLink.jsx" - Get autocomplete
- Change back to absolute:
"/snippets/tsdocs/RefLink.jsx"

