- Is ns/ace-sonata-bundle a Laravel package I can install with Composer?
- No. Despite being catalogued in a Laravel/PHP context, this is a Symfony bundle built for SonataAdminBundle, which is a Symfony-only admin generator. Its service definitions, form types, and Twig templates all assume the Symfony kernel and dependency injection container, so it cannot be autoloaded or used meaningfully inside a Laravel application. Treat any Laravel-compatibility claim for this package as a catalogue error and correct the record.
- How do I install ns/ace-sonata-bundle?
- You would install it with a standard Composer require inside a Symfony application that already has SonataAdminBundle configured. There are likely no tagged releases given the package's age and lack of activity, so expect to pin a dev-master constraint rather than a stable version. After installing, you would register the bundle in your kernel bundles file and configure whatever Ace asset integration it depends on. Verify the require block resolves against your installed Sonata Admin version before writing any code.
- Which Symfony, PHP, and Sonata Admin versions does this bundle support?
- The README excerpt does not state version constraints, so you must inspect composer.json directly to see the pinned Symfony, PHP, and Sonata Admin requirements. Glue packages of this vintage frequently pin old versions that deadlock against modern Symfony releases. Run a dry-run Composer resolution against your exact stack to confirm compatibility before committing to it.
- What does this bundle actually add to Sonata Admin?
- It is a thin adapter that bridges Sonata Admin's form and field system to an Ace code editor asset bundle, so admin forms can render a syntax-highlighted code editor widget for text, JSON, or configuration fields. Such packages are typically only a few hundred lines: a form type, a Twig template, a service definition, and an asset include. Confirm whether it ships a form type, a Twig extension, or both by reading the source before assuming capabilities.
- Does it work with current Sonata Admin and Symfony 5 or 6?
- Unverified. With one star, zero dependents, and no issue history, there is no evidence of anyone running this against a modern Sonata Admin release. Sonata itself has been moving toward Symfony UX and Webpack Encore, while Assetic-era Ace bundles are largely abandoned, so a glue package sitting between them is likely stale. The only reliable answer comes from a proof-of-concept render in a scratch Symfony app pinned to your Sonata Admin version.
- How does the bundle load Ace editor assets — Assetic, Webpack Encore, or a CDN?
- The overview does not specify, but packages of this era commonly relied on Assetic or a remote CDN reference. If it depends on an abandoned Assetic-based Ace bundle, you will likely need to replace that with a direct npm Ace dependency wired through Webpack Encore. Check the Twig templates and any asset configuration to see how scripts and stylesheets are injected into the admin page.
- Is ns/ace-sonata-bundle safe to use in production?
- Technical risk is high for reasons unrelated to code quality: a single maintainer, zero downstream users, and two moving upstream dependencies. There is no issue history to mine for known breakages and probably no CI or tests, so regressions would surface only in your own environment. It is only defensible in production if you fork it, tag an internal release, and pin it alongside a specific Sonata Admin minor version.
- Are there tests or CI for this bundle?
- Nothing in the available information indicates tests, CI configuration, or a release history. Given the package's size and inactivity, you should assume there is no automated safety net. If you adopt it, plan to write your own smoke test that renders one admin form with the Ace widget and asserts the editor markup appears.
- What are the alternatives to this bundle for a code editor field in Sonata Admin?
- The need for a syntax-highlighted editor field in an admin panel is legitimate; this particular implementation is the questionable part. You can reimplement it as your own Sonata form type plus an Encore entry point loading Ace or CodeMirror from npm, which at this size is roughly a day of work. That approach removes an unmaintained third-party from your critical path and gives you control over asset loading and Ace modes.
- Should I adopt this package or just copy the implementation?
- Mine it rather than adopt it. At a few hundred lines, the package is better treated as a reference implementation: read the form type and Twig template, then rebuild them internally with a direct npm Ace dependency through Encore. Adoption only becomes rational if the integration surface turns out to be substantially larger than expected, such as multi-field configuration, custom Ace modes, and theme handling. Verify the actual line count before deciding, and if you do adopt, run a proof-of-concept render first and pin a forked tag.