- How do I install mydnic/volet in a Laravel application?
- Install it with Composer by requiring mydnic/volet, then follow the package docs to publish its configuration and frontend assets. Volet is designed to be dropped into an existing Laravel app rather than forked or hosted standalone. The v2.2.3 release does not add migrations, config keys, service-provider registrations, or middleware, so there is no extra wiring beyond the documented publish steps.
- Which Laravel and PHP versions does Volet v2.2.3 support?
- The dependency bumps in v2.2.3 track the Laravel 13 line, with laravel/framework at 13.16.1 and orchestra/testbench at 11.2.0 in the test matrix. That points to a Laravel-13-era application on PHP 8.3 or newer. Applications still on Laravel 12 or earlier should stay on the prior release track and check the declared framework constraint before upgrading.
- Do I need Node or a build pipeline to use Volet's feedback widget?
- Volet ships a bundled frontend layer with a Vite/esbuild build chain and jQuery in the asset graph, but you normally consume the compiled assets rather than build them yourself. A Node pipeline is only needed if you publish and customise the widget's source assets. Standard Composer autoloading plus asset publishing is enough for a typical install.
- Is upgrading from Volet v2.2.2 to v2.2.3 a breaking change?
- No. v2.2.3 is a semver-correct patch with no API surface change, no deprecations, no removed methods, and no schema or config changes. The migration is effectively a no-op: bump the constraint within ^2.2 and run composer update mydnic/volet. If you have published assets, re-publish and clear your view and asset caches, since that is the one manual step the build fix may require.
- Why did my published Volet assets or compiled bundle change after upgrading?
- The only non-dependency commit in v2.2.3 is a build-pipeline correction that fixes a jQuery conflict with terser. That changes compiled output, so any assets you previously published may no longer match the shipped bundle. Re-publish the relevant tag with vendor:publish --force (or rebuild from source) and clear caches if you notice stale or conflicting jQuery behaviour.
- Does Volet render user-submitted Markdown, and could the league/commonmark update change the output?
- If your feedback content is stored or rendered as Markdown, Volet's rendering path likely goes through league/commonmark, which moved from 2.8.2 to 2.9.0 in this release. Crossing a minor boundary is the most plausible source of subtle rendering differences in user-supplied content. Run a visual check on existing feedback entries after upgrading, and confirm whether the package ships a regression test covering that path.
- Could installing Volet cause Composer dependency conflicts with my app's Laravel or Symfony pins?
- The release moves laravel/framework from 13.11.2 to 13.16.1 and Symfony components within 7.4.x. If those are declared as runtime require constraints, apps pinned below those patch levels may hit resolver conflicts. Run composer why-not mydnic/volet if resolution fails, and decide whether to raise your own framework floor or hold Volet at its previous patch.
- Does Volet add database migrations, config keys, or middleware to my application?
- This release adds none of those. Integration is composer require mydnic/volet plus whatever asset publishing or configuration the package documents, and no data migrations or config republishing are required. That keeps the footprint small, but it also means any persistence for feedback entries comes from the package's own documented setup rather than an auto-discovered migration.
- Can I use Volet standalone or on Laravel 12 instead of Laravel 13?
- Volet is built to be installed into an existing Laravel application via Composer and is not intended to be forked or hosted as a standalone service. This release line targets the Laravel 13 track, so Laravel 12 and older apps should remain on the earlier major or minor line. If you need a different hosting model, treat the package as a starting point for your own implementation rather than a supported deployment target.
- Is mydnic/volet v2.2.3 safe to run in production and actively maintained?
- Supply-chain posture looks good: 24 of the 25 changes are Dependabot version pins merged through CI, and the only hand-made commit is a build fix. Residual risk is concentrated in the framework floor drift, the Guzzle and CommonMark transitive updates, and an opaque frontend rebuild whose assets you cannot diff from the release notes alone. Before shipping, verify the declared framework constraint, diff released asset checksums between v2.2.2 and v2.2.3, and smoke-test any Markdown-rendering or feedback-submission paths.