Filament Ace Editor Field Laravel Package

Product Decisions This Supports

• Feature scoping: code-editing inside Filament admin forms. Use this package when the product needs a better-than-textarea input for editable HTML, CSS, JavaScript, JSON, PHP, Markdown, email templates, webhook payloads, configuration snippets, or other structured text. It is a focused UX improvement, not a full IDE.
• Build vs. buy. Buy for the common case: a Filament-native field that wraps Ace Editor with configurable mode, theme, height, placeholders, validation, editor options, extensions, dark-mode theming, and read-only behavior when disabled. Building equivalent Alpine/Ace glue is only justified if the roadmap requires Monaco/CodeMirror-class capabilities such as linting, IntelliSense, collaboration, or AI assistance.
• Roadmap sequencing. Pilot in internal admin tooling first—content templates, integration settings, workflow rules, or API response templates—where the blast radius is limited. Expand to power-user or customer-facing forms only after validation, sanitization, audit logging, and asset-hosting decisions are settled.
• Platform and UX standardization. The package gives product a consistent code-editing field across Filament resources rather than one-off textareas. Mode/theme configuration supports matching the panel’s light/dark UI and tailoring the editor to the content type.
• Risk-aware adoption. Stars and dependents remain low, so ecosystem proof is still thin and single-maintainer bus-factor risk stands. However, release 2.1.0 materially improves the maintenance signal: a new Pest suite plus a CI matrix across PHP 8.2–8.4 and Laravel 11–13 shows the maintainer is testing compatibility rather than shipping blind. Treat it as a tactical dependency: pin versions, pilot narrowly, define a fallback (fork under MIT or swap the field implementation), and avoid making it a critical path for customer-facing code execution.
• Security and compliance decisions. The field edits text; it does not sandbox or execute code. Product must pair it with server-side validation, output escaping/sanitization, authorization, and audit trails for any user-generated HTML/JS/config. Confirm CSP and CDN policy before launch because the package loads Ace assets from a configurable CDN base URL. Note that 2.1.0 moves the default Ace CDN version from 1.32.7 to 1.44.0—an asset-version change that should be treated as a reviewable update, not a silent one.
• Version and asset governance. The 2.1.0 release is non-breaking for the v2/v5 line but includes an asset-version bump and a config-republish step. Product should budget a small regression pass (editor modes, themes, extensions actually used in your panels) whenever the pinned Ace version changes, and should keep the CDN base URL and Ace version under the same change-control as other third-party dependencies.

When to Consider This Package

Consider adopting if:

• The product runs Filament 5.3+ with PHP 8.2+ for v2, or Filament 4.8+ for the v1 line, and needs a lightweight syntax-highlighted field inside Filament forms. Version 2.1.0 is explicitly tested on PHP 8.2/8.3/8.4 against Laravel 11/12/13, which covers current and near-term Laravel upgrade planning.
• The use case is primarily internal admin tooling or controlled power-user editing: templates, snippets, JSON, CSS, HTML, configs, and similar text.
• Basic editor configuration is sufficient: mode, theme, dark theme, height, rows/columns, autosize, editor options, extensions, placeholder, required validation, and disabled/read-only state.
• The team can accept small-package risk and is prepared to pin versions, review upgrades, self-host assets if needed, and fork under MIT if maintenance stalls. The 2.1.0 CI matrix and Dependabot policy (Filament majors ignored per branch, 7-day cooldown on other updates) reduce—but do not eliminate—the concern.
• The organization allows CDN-loaded JavaScript or can configure a self-hosted Ace base path/CSP-compatible asset strategy. If you customize the Ace base URL or version, plan to republish the config to pick up the 1.44.0 default deliberately rather than incidentally.
• Teams can absorb small documentation-level gotchas: height() now correctly documents that a CSS unit is required (e.g. '200px'), so stored or hard-coded numeric heights from earlier examples should be audited.

Look elsewhere if:

• The roadmap requires advanced editor features: real-time collaboration, custom linting, IntelliSense, Git integration, AI-assisted coding, or deep plugin ecosystems. Monaco or CodeMirror are better fits.
• The product needs enterprise support, SLAs, broad adoption evidence, or long-term maintenance guarantees. Improved CI is a positive hygiene signal, not a support contract; low stars and zero dependents still mean you are an early adopter.
• The stack is not Filament—Livewire-only, Inertia, Nova, or another admin framework—or is on an older Filament version outside the supported matrix.
• The use case involves executing or rendering untrusted code. This package is an editor field, not a security boundary; if safe code execution is required, evaluate sandboxing and review architecture first.
• Strict no-third-party-CDN or supply-chain constraints apply and the team is unwilling to self-host and maintain the Ace assets. The jump to Ace 1.44.0 is a reminder that the asset dependency moves independently of the PHP package.
• Accessibility, mobile editing, or highly branded editor UX are hard requirements that need deeper evaluation than the package documents.

How to Pitch It (Stakeholders)

For executives: This is a low-cost, MIT-licensed Filament field that lets teams edit code-like content—HTML templates, JSON configs, CSS, snippets—inside the admin panel instead of switching to external editors or asking engineering for small changes. It accelerates internal tooling and reduces handoffs. The latest release (2.1.0) is a maintenance release with no breaking changes, and it adds automated testing across supported PHP and Laravel versions, which slightly improves our confidence in the dependency. It is still an early-stage package with limited adoption, so the recommendation remains a contained pilot rather than a platform-wide mandate. Success should be measured by reduced cycle time for template/config changes, fewer developer interrupts, and lower error rates from syntax-highlighted editing. Keep risk low by limiting the first rollout to internal admin screens, pinning versions, enforcing validation/sanitization, and retaining a fork/fallback path.

For engineering: This is a drop-in Filament form component, AceEditorInput, with fluent configuration for Ace mode, theme, dark theme, height, rows/cols, autosize, editor options, extensions, placeholders, and disabled/read-only state. It publishes a config file for CDN base URL, extensions, editor defaults, and dark-mode behavior. Install via Composer, configure the field, and validate assets/CSP in the target panel. Changes in 2.1.0 to account for during rollout: the default Ace CDN version moved from 1.32.7 to 1.44.0—republish the config if you had customized it, and re-verify the modes/themes/extensions you actually use against the newer Ace build; height() requires a CSS unit ('200px', not 200), per the corrected README; and the build tooling moved to bun with unused ace-builds/npm-run-all2 dev dependencies removed (published distribution is unchanged, so no runtime impact). Note that Filament major-version bumps are intentionally ignored by Dependabot per branch, meaning Filament upgrades are handled deliberately by the maintainer on a release cadence—plan your own Filament upgrade testing accordingly. Key caveats: the package is still small and single-maintainer, tightly coupled to Filament major versions, and depends on Ace assets loaded from a configurable CDN. Recommend a one-form pilot, version pinning for both the Composer package and the Ace CDN version, explicit sanitization/escaping for stored content, and a documented fallback to self-hosted assets or a custom field if maintenance or requirements change.