- Is netbull/foundation-emails-bundle a Laravel package?
- No. It is a Symfony bundle that wraps Foundation for Emails and Inky, despite being evaluated alongside Laravel PHP packages. For a Laravel application, installing Symfony bundle conventions creates an unnecessary dual-framework mismatch. Prefer a Node sidecar compilation step or a maintained MJML-to-Blade path instead.
- How do I install netbull/foundation-emails-bundle in a Symfony app?
- You would install it with Composer and register the bundle in your Symfony application, then add its configuration for template and asset paths. Because the package has minimal ecosystem validation, verify the exact bundle class and config keys against the repository before wiring it into CI. Treat it as build-time tooling rather than a runtime mailer.
- Does foundation-emails-bundle work with Laravel or only Symfony?
- It is designed for Symfony and expects Symfony service container, configuration, and Twig conventions. Laravel does not natively consume Symfony bundles, so forcing it in adds framework coupling for a problem better solved outside the application container. Use a standalone Inky or MJML build step if you are on Laravel.
- What license does netbull/foundation-emails-bundle use?
- The technical assessment flags AGPL-3.0 as the package license, which carries network-use source-availability obligations under section 13. Many organizations blanket-ban AGPL in product dependencies, so legal sign-off should come before engineering investment. Confirm the license in the repository and your distribution model before adopting it.
- Do I need Node, Sass, or Inky installed to use this bundle?
- Likely yes. Foundation for Emails compilation depends on a Node toolchain with foundation-emails, Inky, and Sass, and the bundle is primarily glue around that build process. You would need to provision and pin Node in CI and deploy images. That is a second runtime to maintain even though the bundle itself is PHP.
- What are good Laravel alternatives to Foundation for Emails for responsive HTML emails?
- For Laravel, an MJML-to-PHP or MJML-to-Blade pipeline is usually a better fit than a Symfony bundle. A small Node sidecar can compile Inky or MJML templates into Blade partials during CI, keeping your runtime container clean. Choose a maintained path and avoid adopting a zero-star wrapper as production infrastructure.
- Is Foundation for Emails still maintained and safe for production?
- Upstream Foundation for Emails is widely described as being in maintenance mode, with a shrinking pool of developers familiar with Inky. The bundle itself has zero stars, zero dependents, and a single maintainer, so the bus factor is one. Verify whether upstream Sass and Node dependencies still receive security patches before production use.
- How should I test responsive email rendering across Outlook, Gmail, and Apple Mail?
- Compile one representative transactional email, such as a welcome or receipt message, and diff it against your current production pipeline across your client matrix. Add snapshot tests for the compiled HTML and use a rendering service such as Litmus or Email on Acid for visual checks. Define who owns the compiled artifacts and how regressions are caught in CI.
- How does foundation-emails-bundle integrate with Symfony Mailer and Twig?
- It integrates Foundation for Emails and Inky with Symfony configuration and Twig conventions, producing table-based responsive HTML that you can pass into Symfony Mailer. It is a build-time asset compiler rather than a runtime mailer, so it does not replace your mail transport. Confirm the actual delta versus calling the Inky CLI directly before relying on it.
- Can I use foundation-emails-bundle if my company bans AGPL dependencies?
- If your organization bans AGPL, do not adopt this bundle without a decisive legal review. The AGPL network clause can oblige source disclosure for services interacting with users, and forking the package inherits the same obligations. A direct Inky CLI build step or an MJML-based pipeline avoids adding an AGPL PHP dependency to your product.