- Is luperi/page-annotator-bundle a Laravel package?
- No. It is a Symfony bundle, so it has no Laravel service provider, no package discovery manifest, and no native Laravel integration path. Using it in a Laravel application means either hand-wiring Symfony dependency injection and HttpKernel services inside Laravel or porting the useful logic into Laravel-native code. Treat it as reference material and reusable front-end assets rather than a drop-in Composer dependency.
- Can I install luperi/page-annotator-bundle in a Laravel app with Composer?
- Composer may resolve it, but installation alone will not give you a working Laravel integration. There is no provider registration, no configuration publish path, and no Laravel routes or migrations. The technical assessment recommends against adding it to a Laravel composer.json because it introduces Symfony surface area without an owned integration layer.
- Which Laravel and PHP versions does this annotation bundle support?
- The available description does not state a supported Laravel or PHP matrix, so you must inspect composer.json require constraints before assuming compatibility. The assessment flags it as plausibly Symfony 2 or 3 era and potentially incompatible with PHP 8.1+ and Laravel 10, 11, or 12. Validate resolution against your exact PHP, Laravel, and Octane matrix before any adoption decision.
- How does Page Annotator Bundle persist annotations?
- The bundle uses Doctrine-backed storage with a configurable annotation entity. Annotations are tied to the page and DOM element they belong to so feedback remains contextual. The spike should confirm the exact schema, whether storage is database, file, or session, and whether that schema can be translated into an Eloquent migration.
- What is involved in porting this Symfony bundle to Laravel?
- The realistic path is to extract the vanilla-JS overlay and CSS, then reimplement persistence natively in Laravel. That typically means one annotations migration with polymorphic annotatable_type and annotatable_id, user_id, selector or path, coordinates, body, and timestamps, plus an Eloquent model, an API controller in routes/api.php, and an authorization policy. If the bundle is mostly front-end, budget roughly one to three engineer-days; if server-side Symfony coupling is substantial, budget one to two weeks and accept permanent maintenance.
- Does this package work with Laravel Blade, Livewire, or Inertia?
- There is no native Blade, Livewire, or Inertia integration. The bundle's Twig helper is Symfony-specific and will not work in Laravel, so you would replace it with a Blade directive, a shared JavaScript include, or a front-end component. The overlay itself may be reusable if the source confirms it is framework-agnostic vanilla JavaScript.
- Is the page annotator safe against XSS when storing user comments?
- That is unresolved in the available description and must be answered by a source read. Check whether the bundle accepts, stores, and re-renders user-supplied HTML, and whether it sanitizes on input or output. Any port should sanitize annotation bodies, enforce a Content Security Policy, and treat rendered annotations as untrusted content.
- How should I evaluate this bundle before adopting it?
- Run a time-boxed spike rather than a dependency trial. Read composer.json for PHP and package constraints, measure the front-end-to-PHP ratio, confirm where annotations persist, and check for Twig, Doctrine, or Symfony Forms coupling. Also review the last commit date, open issues, actual feature scope versus the README, and whether any test suite exists.
- What are the alternatives to using this Symfony bundle in Laravel?
- The preferred alternative is to build a small Laravel-native annotation feature using the bundle only as a design reference and asset source. You can vendor the JavaScript and CSS overlay, then own the migration, model, API routes, and policy. A Laravel-native annotation package or a focused in-house implementation will usually be cheaper to maintain than bridging two frameworks in one process.
- Is luperi/page-annotator-bundle actively maintained and production-ready?
- The assessment describes zero dependents, a 0.14 composite score, and an effective bus factor of one, with no CVE response or deprecation policy. That profile means little production validation and no inherited test suite or community answers. The MIT license is the clean dimension because it materially de-risks a fork-and-own path, but you should still verify recent commits and open issues before relying on it.