Weave Code
Laravel Support Laravel Package
taskforcedev/laravel-support
A Laravel utility package from TaskforceDev offering handy support helpers and shared utilities to streamline common development tasks. Lightweight and easy to drop into any Laravel project to reduce boilerplate and keep your codebase clean and consistent.
Support package for Taskforcedev Laravel packages.
Frequently asked questions about Laravel Support
- What is taskforcedev/laravel-support used for?
- It is a utility package from TaskforceDev that bundles handy support helpers and shared utilities used across TaskforceDev Laravel packages, cutting down on boilerplate. Most teams get it as a transitive dependency when they install another TaskforceDev package, but you can also require it directly in any Laravel app. It also carries a small frontend asset layer used by the package's UI components, so it is not purely PHP.
- How do I install taskforcedev/laravel-support with Composer?
- Run composer require taskforcedev/laravel-support and Laravel's package auto-discovery will register the service provider, so no manual entry in config/app.php is normally needed. If the package publishes assets or configuration, run php artisan vendor:publish with the package's tag. If it ships JavaScript, rebuild your frontend assets with Vite or Laravel Mix afterwards.
- Which Laravel versions does taskforcedev/laravel-support support?
- The supported range is declared in the package's composer.json illuminate/support constraint, so check that file or the Packagist page before upgrading your application. Patch releases sometimes adjust supported Laravel ranges, so re-verify after each bump. If Composer refuses the install, run composer why-not taskforcedev/laravel-support to see exactly which constraint is blocking it.
- Does taskforcedev/laravel-support work with jQuery slim instead of full jQuery?
- Yes, the 1.1.4 patch specifically fixed use of jQuery slim. jQuery slim omits the Ajax and effects modules, so any earlier code path calling $.ajax, $.get, $.animate or $.fadeIn would fail silently or throw when a host app aliased slim globally. Confirm in your own app whether jQuery is a peer dependency you supply or something the package bundles before you upgrade.
- Do I need to publish assets after upgrading taskforcedev/laravel-support?
- If the package publishes compiled JavaScript, the patch will not take effect until you re-publish the assets. Run php artisan vendor:publish --tag=<package-assets> --force and then rebuild your frontend bundle. There should be no config republish or database migration involved in this patch-level release.
- Does the package make AJAX requests, and how are CSRF tokens handled?
- The jQuery slim fix implies the package either removed Ajax usage or forked between slim and full builds, so verify which path your environment takes. If Ajax calls remain, check that CSRF tokens, the X-Requested-With header and Laravel's VerifyCsrfToken or Sanctum cookie flow still behave correctly. Watch the network tab during a manual test to confirm request headers and error handling have not diverged.
- Is it safe to upgrade taskforcedev/laravel-support in production?
- The 1.1.4 change is a patch-level update to the frontend asset layer with no PHP API, config or migration changes implied, so risk is low. The main production concerns are downstream asset pipeline fingerprinting, SRI hashes and CSP nonce assumptions, since bundled asset contents changed. Upgrade on a branch, run your test suite, exercise the affected UI surfaces and then deploy to staging before production.
- How should I test taskforcedev/laravel-support after upgrading?
- Run your application test suite plus any tests the package ships, then manually exercise its UI surfaces such as AJAX-driven tables, modals, autocomplete and inline editing. If you support both jQuery slim and full builds, test under both and compare request headers and CSRF behavior in the network tab. Keep the package behind a feature flag in staging first if it is load-bearing in your UI.
- What are alternatives to taskforcedev/laravel-support?
- If you only need string, array or collection helpers, Laravel's built-in Str, Arr and Collection classes usually cover it without an extra dependency. For package scaffolding and shared tooling, spatie/laravel-package-tools is a common choice. Stay on this package if you are already using other TaskforceDev packages, since it exists primarily to share support code between them.
- Is taskforcedev/laravel-support actively maintained?
- The 1.1.4 release shows ongoing maintenance, with a targeted fix that improves compatibility with jQuery slim environments. Check the GitHub releases and changelog for cadence and for any detail about the asset change before relying on it. Its ongoing maintenance footprint is low, but watch the Laravel version range and jQuery version support on each upgrade.
Weaver
How can I help you explore Laravel packages today?