- How do I install the Filament code editor package?
- Install it with composer require sebastiaankloos/filament-code-editor, then register the plugin or service provider if your Filament version requires it and publish the package assets. After that, drop CodeEditor::make('content')->language('php') into any form schema. Because the package is archived, verify the Composer constraint against your pinned Filament major version before installing.
- Which Filament and Laravel versions does this code editor support?
- The last release was in April 2023, so it targets the Filament v2/v3 and Livewire 2/3 era rather than current releases. There is no guarantee it works with newer Filament majors, Livewire updates, or the Vite-based asset pipeline used by modern Filament plugins. Check the composer.json constraints explicitly and smoke-test on your exact Filament and PHP versions.
- Is sebastiaankloos/filament-code-editor still maintained?
- No. The package is archived with its last release in April 2023, so there are no upstream fixes for Filament version drift, Livewire or Alpine changes, or JavaScript dependency CVEs. The repository is also unknown from the package metadata, leaving no issue tracker or changelog to audit. Treat adoption as vendoring rather than depending on a maintained library.
- How do I configure syntax highlighting, language mode, and theme?
- Configuration happens through fluent methods on the field, for example CodeEditor::make('content')->language('php'). Language modes and themes are part of the underlying JavaScript editor, so available options depend on the bundled editor version. Line numbers and theme selection are exposed as field settings described in the package README.
- Does the editor desync on Livewire re-renders or dirty form detection?
- That is a real risk with Alpine and JavaScript-backed fields inside Livewire forms. Editor state may not survive partial re-renders, and dirty-form detection can miss changes made directly in the editor. Test render, save, reload, and read-only mode on your exact Filament version before relying on it.
- Is the JavaScript editor bundled or loaded from a CDN?
- The package README does not clearly document this, and the transitive JavaScript editor dependency is unaudited. Check the published assets to see whether the editor is vendored or fetched at runtime from a CDN. This matters for supply-chain review, air-gapped environments, and offline admin panels.
- Can I use this field to edit JSON or config files in an admin panel?
- You can, but the field itself provides no server-side validation or sanitization. Pair it with strict validation such as JSON schema checks, linting, and a size cap in your form request or Filament rule. For simple config or JSON editing, a monospace-styled Textarea with validation may deliver most of the value with far less dependency risk.
- How should I test the code editor field in a Laravel app?
- Spike it in a throwaway branch and confirm the field renders, saves, reloads with the stored value, and respects read-only mode. Add a Livewire or Filament form test that asserts the value round-trips through the field. Keep that smoke test in place if you fork the package so future Filament upgrades surface breakage early.
- What are the alternatives to this archived Filament code editor?
- Look at maintained Monaco or CodeMirror wrappers built for your Filament version, or use a native Filament Textarea with monospace styling plus server-side validation. If the requirement is just editing config or JSON, the Textarea approach covers most use cases with zero dependency risk. Confirm the alternative's Filament major version support before designing around it.
- Should I fork this package instead of requiring it from Packagist?
- Fork-and-own is the safer path if the feature is genuinely needed, because the archived package will silently break on the next Filament upgrade. Copy it into a private namespace or VCS repository, pin the underlying JavaScript editor version, and add a compatibility shim for your Filament version. Requiring it directly from Packagist is only reasonable for a non-critical internal tool where breakage is acceptable.