- How do I install matt-daneshvar/laravel-survey in Laravel?
- Install it with composer require matt-daneshvar/laravel-survey, then follow the package's normal Laravel setup: publish the config and migrations, run the migrations, and mount the survey routes. The package is designed around Laravel conventions such as service provider auto-discovery and publishable assets, so adoption is intended to be low-friction. Check the tagged README for exact publish tags and route setup before wiring it into an existing app.
- Does laravel-survey support Laravel 13?
- Yes, v0.6.0 is a Laravel 13.x compatibility release, so it is intended to track Laravel 13. The important caveat is that the release notes do not state whether the illuminate constraints were widened to include 13.x alongside older versions or narrowed to 13.x only. Read composer.json in the v0.6.0 tag before assuming your current Laravel version remains supported.
- Which Laravel versions does laravel-survey v0.6.0 support?
- The v0.6.0 release adds Laravel 13.x compatibility, but the provided evaluation does not confirm which older Laravel versions remain supported. That depends on whether the composer constraints were widened or narrowed in the compatibility PR. Treat composer.json in the tagged release as the source of truth and test against your exact Laravel version.
- Is laravel-survey stable enough for production use?
- Treat it as pre-1.0 software: at v0.6.x the maintainer can make breaking changes in a minor release, so any code written against its models and interfaces is provisional. The project also shows single-maintainer concentration, and the v0.6.0 change is a maintenance compatibility bump rather than a capability release. It can be suitable for production if you pin versions, read the diff, and cover your integration with tests.
- How do I create a survey with multiple question types using laravel-survey?
- The package provides survey, question, and response domain models plus migrations and validation so you can define questionnaires with multiple question types in your Laravel app. You create and manage surveys through those models and the package's public-facing rendering layer rather than building the schema from scratch. Confirm the available question types and rendering approach in the tagged README before designing your UI.
- How does laravel-survey store and validate survey responses?
- Responses are collected and stored through the package's included Eloquent models, migrations, and validation. The scope is a simple survey API inside your Laravel application, not real-time writes to an external analytics store. If you need responses in a separate service or warehouse, plan an export or integration layer.
- Can I customize laravel-survey migrations, config, and routes?
- The package follows standard Laravel package conventions, with publishable config and migrations and routes that you mount in your application. That makes schema and configuration changes possible through published files rather than editing vendor code. Route middleware configurability and production hardening options should be verified in the package source and README, because the provided evaluation flags them as open questions rather than confirmed features.
- How should I test a Laravel app that uses laravel-survey?
- Pin both the package version and your Laravel version, then test the integration with your application's normal test suite, including migration and response-validation paths. The provided evaluation does not confirm a documented CI matrix across multiple Laravel versions, so do not assume broad framework coverage. If you rely on specific question types or route middleware, add focused tests for those behaviors.
- How do I upgrade from laravel-survey v0.5.1 to v0.6.0?
- First read composer.json in the v0.6.0 tag to see whether the Laravel 13 compatibility change widened or narrowed the illuminate constraints. If constraints were widened, v0.6.0 can be treated as a drop-in patch and validated with your existing tests. If they were narrowed to Laravel 13.x only, sequence the framework upgrade and package upgrade together as a coupled project.
- Is laravel-survey actively maintained, and what alternatives should I consider?
- The project is tracking Laravel's release cadence, and v0.6.0 was contributed via a Laravel Shift bot, which is a positive automation signal, but the evaluation describes a low-velocity, single-owner project rather than a team-backed one. The provided context does not name specific alternative packages; if you need alternatives, compare options on Eloquent coupling, Laravel version constraints, maintenance model, and whether survey responses must live outside your Laravel database. Pin versions and review the changelog and composer constraints before adopting or upgrading.