next-intl-dot-notation-error
CommunityFix next-intl dot keys by nesting translation objects.
AuthorHankanman
Version1.0.0
Installs0
System Documentation
What problem does it solve?
next-intl often throws INVALID_KEY when translation keys contain literal dots, which prevents app startup and breaks translations. This Skill provides a proven approach to convert flat key structures that use dots as characters into a nested object structure suitable for dot notation.
Core Features & Use Cases
- Convert flat keys containing literal dots into nested objects, e.g., "email.notification.booking" -> { email: { notification: { booking: ... } } }.
- Update code references to use dot notation for nested lookups (e.g., t('categories.email.notification.booking')).
- Guidance for migration across locales and ensuring consistency across files.
Quick Start
- Identify files with problematic keys.
- Apply the transformation to create nested structures in all locale files.
- Test translations load and dynamic access works.
Dependency Matrix
Required Modules
None requiredComponents
Standard package💻 Claude Code Installation
Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.
Please help me install this Skill: Name: next-intl-dot-notation-error Download link: https://github.com/Hankanman/claude-config/archive/main.zip#next-intl-dot-notation-error Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
Agent Skills Search Helper
Install a tiny helper to your Agent, search and equip skill from 223,000+ vetted skills library on demand.