- How do I install pekhota/nova-scroll-buttons in my Laravel Nova app?
- Install it with Composer using composer require pekhota/nova-scroll-buttons. Because it is a Nova admin-layer package, no application code changes are typically required beyond the install and an optional asset or config publish step. Pin the exact version (for example v1.0.4) rather than a caret range while you validate it in a staging Nova environment.
- Does this package support Laravel Nova 13?
- Yes. Release v1.0.4 explicitly added Laravel Nova 13 support. That release appears to be additive compatibility work, so it delivers value only if your application is on the Nova 13 line. If you are on an older Nova major, check the composer.json constraint before assuming compatibility.
- Will this package work with older Nova versions like Nova 4 or Nova 5?
- That is not stated in the available release information, so treat it as unverified rather than assumed. Nova-versioned packages usually encode support through constraints in composer.json, and a constraint change can quietly drop or widen support. Read the package's composer.json and the v1.0.4 diff to confirm which Nova majors are actually permitted.
- How do I change the position of the scroll-to-top and scroll-to-bottom buttons?
- The package exposes configurable position and styling, so you adjust placement through its published configuration rather than editing vendor files. Publish the package config if it is not already present, then set your preferred position and recompile or re-publish assets as required. Keep the config in version control so upgrades do not silently overwrite your placement choices.
- Do the scroll buttons appear on all Nova pages or only resource index pages?
- The package is described as targeting Laravel Nova resource index pages, where long lists make scrolling tedious. It works with existing Nova resources out of the box, so you do not need to register each resource individually. If you need buttons on custom tools or dashboards, verify the behaviour in a staging environment first.
- Do I need to publish assets, config, or run npm to use it?
- The install is described as simple, and Nova tool packages usually ship precompiled assets so no front-end build step is required. Some packages still expose publishable config or assets, so check the README for an artisan vendor:publish command. Confirm whether migrations, config, or assets are published, since those need re-publishing on upgrade.
- Can I customise the styling of the scroll buttons to match my Nova theme?
- Yes. The package advertises configurable position and styling, so you can align the floating buttons with your Nova theme rather than accepting the defaults. Typical adjustments cover placement, colours, and sizing through the published config or CSS overrides. Avoid editing vendor files directly so your customisations survive composer updates.
- Does adding scroll buttons affect performance on long Nova index pages?
- The feature is a small front-end enhancement that listens for scroll position and toggles two floating buttons, so overhead is minimal compared with the resource query behind the page. The real performance cost on long indexes comes from pagination and filter choices, not the buttons. If you notice jank, throttle the scroll handler or reduce button animation in your styling overrides.
- Is pekhota/nova-scroll-buttons actively maintained and safe for production?
- The v1.0.4 release tracking a Nova 13 major is a positive maintenance signal, but there is no published CI matrix or issue history available to confirm test coverage. Bus factor is unknown, which is common for small admin-layer packages. It is a reasonable fit for internal back-office panels and easy to remove, but pin the version and stage it before production rollout.
- What are the alternatives if I do not want another Nova dependency?
- Because this is presentation-only admin tooling, you can replicate it with a small custom Nova card, tool, or a few lines of CSS and JavaScript injected into the Nova layout. That avoids an extra Composer dependency and its Nova-major upgrade cadence entirely. The trade-off is that you own the maintenance, whereas the package gives you a one-command install.