- How do I install iperamuna/filament-ace-editor in a Laravel application?
- Install it with Composer using composer require iperamuna/filament-ace-editor. Filament plugins usually register themselves through package discovery, but check the README for any service provider or asset publishing step. After installation, confirm the field class is available in your Filament form schema.
- Does this package support Laravel 13 and PHP 8.4?
- Version 1.3.0 is a compatibility release that adds declared support for Laravel 13 and PHP 8.4. Before upgrading, check the actual composer.json constraints to see whether Laravel and PHP requirements were widened to allow older versions or replaced with 13-only and 8.4-only. If your application still runs Laravel 11 or 12, a widened constraint is a drop-in, while a replaced constraint forces an application upgrade.
- How do I add an Ace code editor to a Filament form?
- Use the package's Ace editor field inside your Filament form schema, typically with a call such as AceEditor::make('content'). Place it alongside other fields in the schema and pass any language, theme, or editor options the field exposes. Because it is a Filament form component, it participates in validation, state binding, and Livewire updates like other fields.
- Can I use the Ace Editor in Filament infolists, not just forms?
- Yes. The package description states it supports both Filament 5 Forms and Infolists. In an infolist, the editor is typically used as a read-only or display-oriented code viewer, so check whether the field supports a readonly or disabled state. The same field class should work in both contexts, but verify rendering and state behavior in your Filament version.
- How do I change the Ace Editor language mode or theme?
- The package advertises syntax highlighting, themes, and configurable options, so language mode and theme are usually set through fluent methods on the field or through an options array. Check the README for the exact method names, such as language or theme, and the accepted Ace mode and theme identifiers. If no per-field method exists, the package may expose a config file you can publish and edit.
- Is iperamuna/filament-ace-editor compatible with Filament 4 or Filament 3?
- The package is described as an Ace Editor implementation for Filament 5 Forms and Infolists, so its supported Filament version is 5.x. There is no indication in the release notes that Filament 4 or 3 are supported, and a Laravel 13 compatibility bump does not imply older Filament support. Confirm the filament/filament constraint in composer.json before installing in an older admin panel.
- What Laravel and PHP versions does version 1.3.0 require?
- Version 1.3.0 upgrades the package to Laravel 13 and PHP 8.4 support, but the release note does not say whether those constraints were widened or made exclusive. Read composer.json to see whether it allows ^11.0|^12.0|^13.0 and ^8.2|^8.3|^8.4, or only ^13.0 and ^8.4. That difference determines whether existing Laravel 11/12 and PHP 8.2/8.3 applications can upgrade without a framework jump.
- How do I test a Filament form that uses the Ace Editor field?
- Write a Filament form or Livewire test that mounts the form, fills the Ace editor field, and asserts the saved state, just as you would for any other field. Because Ace is a JavaScript editor, browser-level interactions need a Dusk or Playwright test if you want to exercise the editor widget itself. Also run your test suite on the PHP version you deploy, since PHP 8.4 deprecations can appear as notice-level noise.
- Is this package production-ready and actively maintained?
- The package is a focused Filament field integration, and version 1.3.0 shows the maintainer is keeping it aligned with newer Laravel and PHP releases. Maintenance signals are limited to a single compatibility commit in that release, so review the repository history, open issues, and release cadence for your risk tolerance. For production, pin a version, run your own test suite, and verify the Composer constraints.
- What are alternatives to this package for code editing in Filament?
- Alternatives include Monaco Editor integrations, CodeMirror-based Filament fields, or a custom Filament field wrapping a JavaScript editor such as Ace directly. The right choice depends on whether you need read-only viewing, JSON validation, theme customization, or full IDE features. Compare package maintenance, Filament 5 compatibility, and whether the editor assets are bundled or loaded from a CDN.