Laravel Arabic Numbers Middleware Laravel Package

Product Decisions This Supports

• Localization/MENA roadmap decisions: Supports launching or improving Arabic-first experiences where users type Arabic-Indic digits (١٢٣٤٥٦٧٨) into forms, search, OTP, phone, ID, payment, or account fields and the backend expects Western digits (12345678).
• Input normalization strategy: Informs whether to normalize numerals at the HTTP boundary via middleware, in form requests/validation, at the frontend, or in domain services. The package favors a centralized Laravel middleware approach.
• Build vs. buy: For a narrow Laravel-only need, this is a small MIT utility that can be cheaper than building and maintaining custom numeral-conversion middleware. PM should still budget for pinning/forking and regression tests because adoption is low and the last release is 2023.
• Conversion and support-cost reduction: Reduces avoidable form errors, failed validations, duplicate customer records, and support tickets from Arabic-speaking users entering localized numerals.
• Feature scoping: Helps decide whether Arabic numeral handling is a launch blocker for Arabic markets or a nice-to-have. If numeric input is core to onboarding, checkout, KYC, or support workflows, treat normalization as part of the localization acceptance criteria.
• Architecture guardrail decision: The middleware may normalize request input broadly. PM should push for field-level or route-level scoping so free-text, names, tokens, hashes, content, and semantically meaningful codes are not silently transformed.

When to Consider This Package

• Your product is Laravel/PHP and needs to accept Arabic-Indic or Eastern Arabic numerals in request input without asking users to switch keyboards or mentally translate digits.
• The problem is narrow and well-defined: digit normalization for numeric fields, not full RTL, translation, currency, date, or locale-aware formatting.
• You can scope normalization to known fields/routes and add tests for forms, validation, APIs, and edge cases such as mixed Arabic/Latin text, decimals, leading zeros, and identifiers.
• You are willing to pin the dependency or fork it if needed, and verify compatibility with your Laravel/PHP version given the 2023 last release and modest 19-star adoption.
• You want a low-effort, transparent middleware layer rather than introducing a broader localization platform or frontend input-mask project.

Look elsewhere or build a small in-house normalizer if:

• You need full internationalization: ICU message formatting, pluralization, locale-aware number/currency/date display, RTL layout, and translation management.
• The app must preserve user-entered numerals in content, legal text, names, messages, or identifiers where conversion would change meaning.
• You need strong maintenance guarantees, security review, or enterprise support; a 19-star package with a 2023 release should be treated as a utility to vet, pin, and possibly own.
• Your numeral handling belongs primarily in the frontend input layer or a shared validation/domain layer across non-Laravel services.
• You need complex transliteration beyond Arabic-Indic to Western digits, such as mixed-script parsing, Arabic decimal separators, or locale-specific formatting.

How to Pitch It (Stakeholders)

For executives: This is a small, low-cost localization enabler for Arabic-speaking markets. It helps users enter numbers naturally while keeping backend validation and data storage consistent, which can reduce form abandonment and support friction in onboarding, checkout, and account flows. It is not a strategic platform bet; treat it as a tactical utility with a maintenance check, pinned version, and tests.

For engineering: It is a Laravel middleware that normalizes Arabic/Eastern numerals to Western digits in requests. Adopt only with route/field scoping and regression tests, because global request mutation can affect free-text and identifiers. Given the low star count and 2023 last release, verify framework compatibility and be prepared to fork or replace it with a short custom middleware if the package becomes stale.