Weave Code
Laravel Nps Laravel Package
maize-tech/laravel-nps
Add Net Promoter Score surveys to your Laravel app. Create NPS surveys, collect and store responses, and calculate your score with configurable models, routes, and views, plus customizable migrations for quick setup.
Easily integrate custom-made NPS (Net Promoter Score) into your application
Frequently asked questions about Laravel Nps
- How do I install maize-tech/laravel-nps in a Laravel app?
- Install it with composer require maize-tech/laravel-nps, then publish the package config and migrations, run php artisan migrate, and mount the survey surface. The package registers its own service provider, so no manual wiring is required in the app. Diff the published migrations before running them on a shared database.
- Does laravel-nps 2.2.0 support Laravel 11?
- Yes. Version 2.2.0 is a single-change release whose only content is Laravel 11.x compatibility via PR #9, with no new features and no stated breaking changes. Before adopting it, check the composer.json constraint to see whether it is ^11.0 only or a disjunction covering 9, 10, and 11.
- Does this package still support Laravel 9 and 10, or is 2.2.0 Laravel 11 only?
- The release notes do not state this explicitly, so the practical check is the updated composer constraint in the 2.2.0 tag. A disjunction such as ^9.0|^10.0|^11.0 means you can stay on Laravel 10 and still upgrade the package. If the constraint is ^11.0 only, treat the package bump as part of a framework upgrade and sequence it accordingly.
- What PHP version does laravel-nps require?
- Laravel 11 raised the PHP floor to 8.2, so an L11-compatible release generally requires PHP 8.2 or higher. Confirm the exact minimum in the package's composer.json before deploying. If the requirement was bumped, make sure your CI matrix and production runtime match it.
- How do I publish the config and migrations for laravel-nps?
- Use the standard vendor publish workflow to export the package config and migrations into your application. Re-publish config only if the changelog mentions new keys, and always diff published migrations against the package originals before running them. Published config drifting from package defaults is a common operational failure mode to watch for.
- How does laravel-nps calculate the Net Promoter Score?
- The package stores individual survey responses and provides score calculation on top of them, so you can derive your Net Promoter Score from collected data. Responses are classified as promoters, passives, and detractors and scored using the standard NPS formula. Because responses are Eloquent models, you can also build your own aggregate queries when you need custom reporting.
- Can I customize the NPS survey models, routes, and views?
- Yes. Models, routes, and views are configurable, and migrations are published so you can adapt the schema to your application. That configurability is the main reason to pick it over bespoke instrumentation when you want NPS out of the box. Keep local edits minimal where possible, since heavy customization makes future package upgrades harder.
- Is laravel-nps compatible with Vite-based Laravel 11 frontends?
- Laravel 11 defaulted new applications to Vite, so confirm that any published frontend assets or build assumptions in the package work with your setup. The safe approach is to exercise the survey capture flow end to end in staging on a Vite-based app before rollout. Apps still on Mix are likely fine as well, but that combination is also worth verifying.
- How do I upgrade an existing install to laravel-nps 2.2.0?
- Treat 2.2.0 as a patch-level upgrade: pin your current version, verify the new composer constraints in a scratch branch, then run composer update maize-tech/laravel-nps. Re-publish config only if the changelog indicates new keys, and diff published migrations before running them. Run the package and application test suites in CI on your target PHP and Laravel pair, then exercise the survey flow in staging before production.
- Is laravel-nps actively maintained, and what should I consider before adopting it?
- It is a small, single-maintainer project with infrequent releases and community-only support through GitHub issues. Plan for the possibility of lagging behind future Laravel majors, and assign internal ownership to the team that owns customer feedback or analytics. If you need a vendor SLA or guaranteed maintenance, weigh that risk against building lightweight NPS capture in house.
Weaver
How can I help you explore Laravel packages today?