Technical Evaluation

Modular and Laravel-Aligned: The package follows Laravel’s translation conventions (resources/lang/vendor/) and integrates natively with the trans() helper, LanguageServiceProvider, and Blade directives. This ensures zero architectural disruption and leverages existing caching (e.g., config('app.fallback_locale')) without custom infrastructure.
Decoupled Data Layer: Currency names are stored in isolated JSON files per locale, enabling independent updates or overrides. This aligns with Laravel’s vendor-agnostic design and avoids polluting core translation files.
Performance Neutral: Translations are cached identically to Laravel’s default language files, introducing no runtime overhead. Ideal for latency-sensitive applications (e.g., real-time dashboards, global checkout flows).
Extensibility for Edge Cases:
- Supports custom locales via lang:publish + manual overrides.
- Handles hybrid currency codes (e.g., crypto) through programmatic fallbacks (e.g., trans('...', [], 'en', 'fallback')).
- Compatible with Laravel Mix/Pulse for dynamic locale switching in SPAs.

Zero-Breaking-Change Compatibility: Backward-compatible with Laravel 8–13, PHP 8.1+, and Pest 3. Recent releases (1.5.0+) explicitly support Laravel 11–13, with no deprecations.
Five-Minute Integration:
1. Install: composer require laravel-lang/native-currency-names.
2. Publish: php artisan lang:publish --provider="LaravelLang\NativeCurrencyNames\NativeCurrencyNamesServiceProvider".
3. Use: __('native-currency-names::currency.USD', [], 'ja') → "ドル".
Frontend/Backend Agnostic:
- Blade: @currency('USD', 'ja') (custom directive) or raw __() calls.
- APIs: trans('native-currency-names::currency.' . $currency, [], $locale).
- CLI/Queues: Directly access via app('translator').
No Dependency Conflicts: Isolated namespace (LaravelLang\NativeCurrencyNames) and no external HTTP/API calls, reducing risk of version skew or downtime.

Risk	Severity	Mitigation Strategy
Locale Coverage Gaps	Medium	Validate target locales against supported list. Use `trans()` fallbacks (e.g., `trans('...', [], 'ja', 'en')`) for unsupported combinations.
Currency Code Mismatches	Low	Enforce ISO 4217 codes (e.g., `USD`, not `US`) via validation (e.g., `Illuminate\Validation\Rule::in(['USD', 'EUR', ...])`).
Caching Invalidation	Low	Clear translation cache (`php artisan cache:clear`) after manual locale updates or use `trans()`’s built-in cache busting.
Dynamic Currency Logic	Medium	For non-ISO codes (e.g., crypto), extend the package or use a hybrid key (e.g., `trans('native-currency-names::custom.BTC', [], $locale)`).
RTL/LTR Rendering Issues	Low	Test currency names in RTL locales (e.g., Arabic `دولار`) with CSS `direction: rtl` and ensure symbols (e.g., ₹, ¥) align correctly.
Future Laravel Version Risk	Low	Monitor Laravel Lang’s roadmap for Laravel 14+ support. Package’s active maintenance (last update: March 2026) reduces risk.

Locale Prioritization:
- Which top 5 locales require immediate support (e.g., ja, hi, ar)? Are there regulatory requirements (e.g., Japan’s Financial Instruments Act mandates "ユーロ" over "Euro")?
Currency Scope:
- Beyond ISO 4217, do you need support for crypto (BTC, ETH), historical currencies, or custom codes (e.g., internal project codes)?
Integration Points:
- Where will currency names be used? Prioritize:
  - Checkout flows (Blade/API).
  - Admin dashboards (Eloquent/Query Builder).
  - Email templates (Markdown/Blade).
  - Third-party APIs (e.g., Stripe webhooks).
Fallback Strategy:
- Define fallback locales (e.g., ja → en) for unsupported currency/locale pairs. Example: trans('...', [], 'ja', 'en').
Testing Requirements:
- Need automated tests for locale coverage? Suggest using Pest to assert translations:
```
expect(__('native-currency-names::currency.USD', [], 'ja'))->toBe('ドル');
```
Performance SLAs:
- For high-traffic apps, measure translation cache hit ratio post-integration (target: >99%).
Maintenance Ownership:
- Will the team override translations (e.g., for branding) or rely on upstream updates? Document in README.md:
```
# Overriding Translations
Copy `resources/lang/vendor/native-currency-names/` to `resources/lang/` to customize.
```

Integration Approach

Laravel-Centric: Optimized for Laravel’s ecosystem (translation system, Blade, API responses, queues). No framework-specific hacks or monolithic dependencies.
PHP Version Compatibility: Supports PHP 8.1+ (aligned with Laravel 8–13). Tested with:
- Laravel: 8.x, 9.x, 10.x, 11.x, 12.x, 13.x.
- Testing: Pest 3, PHPUnit 10+.
Tooling Integration:
- Laravel Mix/Pulse: Dynamic locale switching in SPAs.
- Laravel Forge/Envoyer: Zero-config deployment (translations are static files).
- Laravel Scout: Localized search results (e.g., "€uro" vs. "ユーロ").
Database Agnostic: No migrations or schema changes required. Works with MySQL, PostgreSQL, SQLite, etc.

Phase	Action Items	Estimated Effort	Dependencies
Discovery	Audit existing currency displays (Blade, APIs, emails). Identify gaps (e.g., hardcoded `$`, missing locales).	2 hours	Product team, design system docs
Integration	1. Install package. 2. Publish translations. 3. Replace hardcoded currency names with `__('native-currency-names::currency.CODE', [], 'LOCALE')`. 4. Test edge cases (fallbacks, RTL).	4 hours	Dev environment, CI pipeline
Validation	1. Manual QA for top 5 locales. 2. Automate tests for critical paths (e.g., checkout flow). 3. Performance benchmark (translation cache hit ratio).	6 hours	QA checklist, Pest/PHPUnit tests
Rollout	Gradual deployment: Start with non-critical pages (e.g., admin dashboards), then checkout, then emails. Monitor error rates (e.g., missing translations).	2 hours	Feature flags, Sentry monitoring
Optimization	1. Cache invalidation strategy for dynamic locales. 2. Custom facade for complex use cases (e.g., `Currency::name('USD', 'ja')`). 3. Document overrides process.	3 hours	Dev docs, internal wiki

Locale Support:
- Out-of-the-box: 100+ locales (e.g., ja, hi, ar, pt_BR, zh_CN).
- Gaps: Use trans() fallbacks or extend the package. Example:
```
// Fallback to English if 'fr_CA' is unsupported
trans('native-currency-names::currency.CAD', [], 'fr_CA', 'en');
```
Currency Codes:
- Supported: ISO 4217 (e.g., USD, EUR, JPY).
- Unsupported: Extend via custom JSON files or hybrid keys (e.g., native-currency-names::custom.BTC).
Laravel Features:
- **Bl