Weave Code
Amp Toolbox Bundle Laravel Package
holadev/amp-toolbox-bundle
A Symfony bundle integrating AMP Toolbox to transform, optimize, and validate AMP HTML. It provides services for server-side AMP rendering, performance enhancements, and validation workflows, helping you deliver faster, mobile-friendly pages with less setup.
Symfony integration for Amp-toolbox-php
Frequently asked questions about Amp Toolbox Bundle
- Can I use holadev/amp-toolbox-bundle in a Laravel application?
- No. This is a Symfony bundle whose entire integration surface is Symfony's DependencyInjection component: a Bundle subclass, a Configuration tree, YAML/XML service definitions and compiler passes registered through the Symfony kernel. Laravel has no mechanism to load or boot a Symfony bundle, so the package is not reachable from a Laravel app. What you can consume is its transitive dependency, the AMP Optimizer PHP library, invoked from middleware, a response decorator, or a Blade post-render hook.
- What does holadev/amp-toolbox-bundle actually do?
- It wires AMP Toolbox into Symfony so you can generate optimized AMP HTML server-side without manually connecting the underlying PHP library. That covers transformations such as server-rendered layout substitution, boilerplate removal, hero-image preloading and srcset generation. It is a configuration and service-wiring wrapper around the AMP Optimizer, not an optimizer written from scratch.
- Is holadev/amp-toolbox-bundle still maintained?
- Barely. There has been roughly one release in about three years, and the current v0.1.6 is a dependency bump rather than a feature or fix release. The project has two stars, no dependents, a single maintainer and no documented security-response channel. There is also no evidence of PHP 8.3/8.4 or Symfony 6/7 support, so treat it as unmaintained until you verify otherwise.
- What license does holadev/amp-toolbox-bundle use, and is it safe for commercial projects?
- It is GPL-2.0, which is anomalous for a Symfony bundle where MIT is the ecosystem norm and the upstream AMP Optimizer libraries are Apache-2.0. Copyleft licensing can carry source-disclosure obligations for a proprietary product that links against it. Nothing in the recent release changes this, so legal review should gate any engineering spend; for many commercial Laravel and Symfony estates it is disqualifying.
- Does holadev/amp-toolbox-bundle support Symfony 6 and Symfony 7?
- There is no support statement in the release notes, so compatibility is unverified. Because the package ships service definitions and compiler passes, an incompatibility typically surfaces as a container compile-time failure rather than a silent degradation. The only reliable way to know is to install it in a scratch Symfony 6 or 7 app and let the container compile.
- Does the v0.1.6 bump to ampproject/amp-toolbox 0.11.2 break the bundle?
- Unverified, and the risk is real: jumping from 0.1 to 0.11.2 is a ten-minor-version move under 0.x semver, where minor versions are explicitly allowed to break. The bundle's service definitions and transformer wiring reference upstream class names and constructor signatures. Nothing in the release notes shows the wrapper's own code was reconciled, and no test matrix was updated, so test it before depending on it.
- How do I install holadev/amp-toolbox-bundle?
- Require it with Composer and register the bundle in your Symfony bundles configuration, then set the bundle's configuration key for the services you need. The lightweight setup is the main selling point for an existing Symfony project. After installing, confirm the container compiles cleanly against the newly pinned 0.11.2 upstream, since that combination is not validated by the maintainer.
- What is the Laravel alternative to this bundle for AMP HTML optimization?
- Use ampproject/amp-toolbox, the AMP Optimizer PHP library, directly in Laravel and skip the Symfony wrapper. It is stack-agnostic and Apache-2.0 licensed, and it can run as middleware, inside a response decorator, or as a post-render step. Pinning the library is strictly safer than pinning a stale, unvalidated wrapper around a moving library.
- Will AMP HTML optimization with this package improve my Core Web Vitals?
- Only for pages that are already AMP HTML. The optimizer performs AMP-specific transforms like boilerplate removal, layout substitution and image preloading; it does not improve ordinary non-AMP pages. If your actual goal is general Core Web Vitals, this is the wrong lever, so confirm your product genuinely emits AMP HTML before investing.
- Is holadev/amp-toolbox-bundle safe to run in production?
- The overall technical risk is high: GPL-2.0 licensing, a single maintainer, no CVE pipeline or issue triage, and a wrapper that is unvalidated against the upstream version it now requires. The appearance of maintenance from a dependency bump is not the same as maintenance capacity. For Laravel or Symfony production systems, prefer the AMP Optimizer library directly, or vendor-fork the bundle if you truly need the Symfony wiring.
Weaver
How can I help you explore Laravel packages today?