- What is binarytorch/larecipe-rtl?
- It is a right-to-left add-on for LaRecipe, the Laravel package that compiles Markdown documentation into a Vue-driven SPA inside a Laravel application. The add-on applies RTL styling and layout adjustments so generated docs read correctly in Arabic, Hebrew, Persian, and other RTL languages. It is positioned as the official RTL companion for the LaRecipe ecosystem rather than a patch to core. The repository is now marked deprecated because LaRecipe V3 ships RTL support out of the box.
- Is binarytorch/larecipe-rtl still maintained?
- No. The package is explicitly deprecated, its last release dates to April 2019, and the repository is archived with roughly three stars and zero dependents. Because the project is archived, there is no path to upstream fixes, security patches, or compatibility updates. LaRecipe V3 is expected to include this functionality natively, which is the recommended replacement path.
- Does larecipe-rtl support Laravel 10 and PHP 8?
- It is very unlikely. A 2019 release implies Composer constraints pinned to PHP 7.x and Laravel 5.x or 6.x, so installation on a current PHP 8 / Laravel 10+ stack would either fail resolution or require the ignore-platform-reqs flag, which should not be approved for a production dependency. Even if it installed, an RTL stylesheet authored against LaRecipe 1.x selectors would silently no-op or only partially apply against modern markup. Treat this as a porting exercise, not an installation.
- How do I install larecipe-rtl in a Laravel project?
- The conventional flow is composer require binarytorch/larecipe-rtl, publish the package assets, and toggle the RTL option in configuration. That flow is only plausible on LaRecipe 1.x running PHP 7.x, which is the narrow stack the package was built for. Given the archived status, the safer approach is to pull the repository, extract the stylesheet and any direction-flipping logic, and commit it into your own asset pipeline instead of adding it to composer.json.
- Which LaRecipe versions is this RTL package compatible with?
- It predates LaRecipe 2.x, so it was authored against the markup, class names, and asset pipeline of the 1.x line. LaRecipe has changed since 2019, meaning selector coverage is unverified for any current release. LaRecipe V3 will include RTL support natively, which removes the need for this add-on entirely. Confirm which LaRecipe major version you run before considering any code reuse.
- How can I add RTL support to LaRecipe docs without this package?
- Harvest the artifact rather than adopt the dependency. Isolate the RTL stylesheet and any direction logic from the repository, then commit that CSS into your application's own asset pipeline alongside your LaRecipe customizations. Diff the selectors against the DOM your LaRecipe version actually emits and fix the gaps, including the navigation drawer side, code block alignment, table direction, breadcrumb order, and search input. Validate the result with real Arabic or Hebrew documentation in a browser before shipping.
- Does larecipe-rtl style only the documentation or the whole Laravel app?
- LaRecipe serves a Vue-driven SPA from within a Laravel application, and this add-on targets the presentation layer of those generated docs. Its scope is the LaRecipe views and assets, not your application's own UI or domain logic. Decide early whether your RTL requirement is docs-only or also extends to the host application shell, since that changes how much CSS you need to own.
- Can I vendor the larecipe-rtl CSS into my own repository?
- That depends on the license, which must be verified before copying anything into your codebase. If the license permits vendoring, commit the stylesheet as a first-party file with a clear provenance note pointing back to the original repository and its archived status. This converts an abandoned third-party dependency into roughly one file of owned CSS, which is cheaper to maintain than a permanent entry in your supply chain.
- What are the risks of adding larecipe-rtl to composer.json?
- Technical risk concentrates in three areas: unverified selector coverage against your LaRecipe version, Composer resolution friction on modern PHP and Laravel releases, and the absence of community signal showing the package ever worked beyond its author's environment. The archived repository means none of these can be fixed upstream. Because the package is small enough to audit in an afternoon and reimplement in less, extraction and vendoring is the lower-risk path.
- What are the alternatives to larecipe-rtl for Arabic and Hebrew docs?
- The primary alternative is upgrading to LaRecipe V3, which includes RTL support natively and is the reason this add-on is deprecated. The other option is a small first-party stylesheet in your own asset pipeline, applied to LaRecipe's output with direction, mirrored layout, and appropriate Arabic or Hebrew font stacks. Both avoid an unmaintained 2019 dependency while achieving the same readability improvement.