Weave Code
Laravel Chunky Laravel Package
jobtech/laravel-chunky
jobtech/laravel-chunky adds chunked, resumable file uploads to Laravel apps, splitting large files into smaller requests and assembling them server-side. It offers a simple API for integrating reliable big-file uploads into forms and storage workflows.
This package handles chunked files upload requests in order to safely save chunked files and, once the upload has been completed, merge all the chunks into a single file.
Frequently asked questions about Laravel Chunky
- What is jobtech/laravel-chunky used for in Laravel?
- jobtech/laravel-chunky is a Laravel package for handling chunked file upload requests. It saves incoming chunks server-side and, when the upload is complete, merges them into a single file, which helps add resumable-style big-file uploads to forms and storage workflows. It is best treated as a tactical upload component rather than a platform dependency until its compatibility and security behavior are verified.
- How do I install jobtech/laravel-chunky via Composer?
- Install it with Composer using composer require jobtech/laravel-chunky, then confirm in the README whether Laravel package auto-discovery registers the service provider and routes. Because the provided excerpt does not document setup details, check for required config publishing, route middleware, CSRF expectations, and storage disk configuration before wiring it into an existing app. Pin the installed version in Composer so future releases do not change upload behavior unexpectedly.
- Which Laravel and PHP versions does jobtech/laravel-chunky support?
- The provided assessment does not confirm a tested Laravel and PHP support matrix, so do not assume compatibility with Laravel 10, 11, or 12. Check the package composer.json constraints, CI configuration, and release notes, then run a non-production spike on your exact Laravel and PHP versions. If your target version is not covered by tests or maintainer metadata, budget for a fork or a different upload package.
- Does jobtech/laravel-chunky support resumable uploads and chunk integrity checks?
- The package is described as handling chunked uploads and merging chunks into a final file, but the provided materials do not confirm resumability semantics or how chunk integrity is verified. Before relying on it, test interrupted uploads, duplicate chunk submissions, concurrent uploads, and final assembly failures. Ask whether upload state is stored on disk, in the database, or in cache, because that determines whether retries are idempotent across requests and servers.
- Which storage disks can jobtech/laravel-chunky use for chunks and final files?
- The overview says the package saves chunks and merges them server-side but does not list supported storage drivers. Verify whether it uses Laravel's filesystem abstraction and whether local, S3-compatible, or other disks are tested for both temporary chunks and the final file. Also confirm permissions, multipart behavior, and whether local temporary storage will break multi-instance deployments.
- How does jobtech/laravel-chunky clean up abandoned chunks?
- The provided materials do not document cleanup guarantees for abandoned chunks or failed assemblies. In a spike, simulate abandoned uploads, expired sessions, and failed merges, then check whether temporary files are removed automatically or require a scheduled cleanup job. Treat orphaned chunks and temp-disk exhaustion as production risks until the package's cleanup behavior is proven.
- Is jobtech/laravel-chunky safe to use for production file uploads?
- Treat production use as requiring a security review because upload handling is security-sensitive. Verify authorization, MIME and size validation, path traversal protections, chunk integrity checks, concurrency handling, temp-file cleanup, and denial-of-service exposure in the package's routes and controllers. The provided assessment recommends wrapping the package behind an internal upload service and running failure and load tests before exposing it to customer-facing flows.
- What frontend contract does jobtech/laravel-chunky expect for splitting and sending chunks?
- The frontend contract is not documented in the provided excerpt, so confirm how the client must split files, name chunks, order requests, and signal completion. Check whether the package ships JavaScript examples or expects a tightly coupled chunk format, because that affects integration cost and replaceability. If the contract is unclear, define your own adapter layer so the frontend is not locked to this package.
- Can jobtech/laravel-chunky scale across multiple app servers or upload directly to S3 multipart?
- The provided assessment warns that app-server chunk proxying increases bandwidth, CPU, temp disk, and request volume, and local temp files break horizontal scaling. It does not confirm direct-to-S3 multipart upload support, so assume chunks pass through Laravel unless you verify otherwise. For large-scale or multi-GB uploads, prefer direct object-storage multipart uploads or a managed upload service, and use this package only where proxying is acceptable.
- Is jobtech/laravel-chunky actively maintained, and should I use it?
- Adoption signals are weak: the package had 44 stars, 0 dependents, a last release date of 2024-02-07, and a low overall score in the provided assessment. That makes stale Laravel compatibility, single-maintainer risk, and undocumented edge cases the main concerns. Use it as a tactical component, pin the version, assign an internal owner, and keep a tested fallback upload path unless you are prepared to fork it.
Weaver
How can I help you explore Laravel packages today?