Weave Code
Profile Bundle Laravel Package
nucleos/profile-bundle
Symfony bundle that adds a ready-made profile area for NucleosUserBundle-based apps, letting authenticated users view and edit account details and change passwords through prebuilt controllers, forms, and routes.
Registration and profile management for symfony
Frequently asked questions about Profile Bundle
- Is nucleos/profile-bundle a Laravel package?
- No. It is a Symfony bundle that registers itself through a Symfony Bundle subclass and a DI extension, and it depends on Symfony's HttpKernel, Routing, Security, Form, EventDispatcher and Twig. Laravel's service provider and Eloquent model have no mechanical equivalent for a Symfony bundle, so it cannot be dropped into a Laravel app.
- Can I install nucleos/profile-bundle in a Laravel application?
- Not in any practical sense. There is no Laravel service provider, no facade, and none of its controllers, forms or Twig templates are wired for Laravel's routing or view layer. Any integration would require a hand-written shim, which costs more than simply rebuilding the profile flow natively with Fortify, Breeze or Jetstream.
- What does NucleosProfileBundle actually provide?
- It adds a ready-made profile area for Symfony apps built on NucleosUserBundle: profile view and edit pages with Twig templates, avatar upload and display, account settings, and a password change flow. Routes, templates and services are configurable. It is designed to integrate with Symfony's security system rather than to be framework agnostic.
- Which Symfony versions does version 2.9.0 support?
- The 2.9.0 release adds Symfony 8 support, which confirms the maintainer is actively tracking Symfony major releases. The release notes do not state which earlier Symfony versions were dropped or which PHP version is now required, so verify the constraints on Packagist and the git tags before relying on them.
- Does it require NucleosUserBundle and Doctrine?
- Yes, it is built around NucleosUserBundle for the user entity contract and almost certainly assumes Doctrine ORM or ODM persistence. That coupling to entity mapping, Symfony Form types and Twig templates is a hard binding, not something 2.9.0 decouples. You would need to implement the expected user interface and plan migrations accordingly.
- How do I install and configure it in a Symfony app?
- Use Composer to require the package, enable the bundle in your kernel, and implement the user interface the bundle expects. Then wire the routes, templates and services through its configuration. For a Symfony and Doctrine project the fit is good, but the real cost is the user entity contract and the migrations that follow.
- Can I port its controllers, forms or services into Laravel?
- Only the framework-agnostic pieces have any chance of surviving a port, such as validators or workflow logic, and only after reading the source. The controllers, Symfony Form types and Twig templates will not port cleanly. For a Laravel codebase it is cheaper to reimplement registration, email confirmation and profile editing natively.
- Is nucleos/profile-bundle safe to use in production?
- Technically it is a small, focused bundle, but the ecosystem signals are thin: roughly 12 stars, zero dependents and a single maintainer with a confirmed bus factor of one. There is no third-party validation or public integration corpus to absorb breakage. Adopting it means depending on that individual's release cadence and on sibling Nucleos packages, so keep a fork as your mitigation.
- What is the maintenance risk of nucleos/profile-bundle?
- The main risk is abandonment by a single maintainer. That risk is somewhat reduced because 2.9.0 shipped Symfony 8 support within the normal release cycle, showing the maintainer tracks Symfony majors actively. Zero issues resolved is consistent with either a stable package or an unused one, and you cannot tell which from the outside.
- What should Laravel developers use instead for profile and avatar management?
- Use Laravel's own stack: Fortify or Breeze for authentication and profile editing, Jetstream when you want team and profile scaffolding, and Laravel's filesystem and storage features for avatar uploads. All of these are first-party, well documented and have large communities. Alternatively, run the Symfony bundle as a separate service behind an API or SSO boundary and federate identity back to Laravel.
Weaver
How can I help you explore Laravel packages today?