Weave Code
Filechunk Bundle Laravel Package
makinacorpus/filechunk-bundle
A Symfony bundle for reliable chunked file uploads: large files are split into smaller parts on the client and reassembled server-side, helping you bypass upload size limits and handle big transfers with Symfony forms and storage.
Javascript file upload widget and form type for Symfony
Frequently asked questions about Filechunk Bundle
- Can I use makinacorpus/filechunk-bundle in a Laravel application?
- Not directly. This is a Symfony bundle built around an HttpKernel bundle class, a DI extension, a Symfony Form type and Twig templates, none of which exist in Laravel by default. Only the server-side chunk assembly logic has portable value, and porting it is estimated at roughly 5 to 8 engineer-days versus 3 to 5 days to build chunked uploads natively on a maintained Laravel foundation.
- What does makinacorpus/filechunk-bundle actually do?
- It provides a JavaScript upload widget that splits large files into smaller chunks on the client and reassembles them server-side. That lets you work around upload_max_filesize and post_max_size limits and handle very large transfers through Symfony forms. The package also ships a Symfony Form type and Twig templates, and the 2.0 alpha line adds a directory listing feature.
- Is makinacorpus/filechunk-bundle still maintained?
- The project is clearly not abandoned, since a 2.0.0-alpha11 release implies sustained development and a modernized PHP and Symfony baseline. However, eleven pre-release iterations means there is no stable API, so you would be pinning a moving target with undocumented breaking changes between alphas. Last known adoption metrics were 1 star, 0 dependents and a quality score of 0.035, which is not a healthy signal for a package gating customer data ingestion.
- Which Laravel versions does makinacorpus/filechunk-bundle support?
- None. There is no Laravel service provider, no bundle registry, no Form component and no Twig layer in this package, so Laravel version support is not applicable. For Laravel you should evaluate native chunked upload approaches such as S3 multipart uploads through Flysystem, Livewire chunked file uploads, or a maintained Laravel chunk-upload package instead.
- What license does makinacorpus/filechunk-bundle use and is it safe for commercial use?
- The license remains unverified in the release notes, but GPL-2.0 should still be assumed based on prior assessment. That is copyleft, which raises a network-use question for SaaS deployments and is close to disqualifying for distributed or on-premise products. Legal review is mandatory before any proof of concept, and renewed upstream activity does not change that requirement.
- How do you install and configure makinacorpus/filechunk-bundle?
- Installation is via Composer with an explicit alpha stability constraint, followed by registering the bundle in your Symfony kernel, configuring the DI extension, and publishing the bundled JavaScript widget assets. That whole installation path assumes Symfony's bundle and Form architecture. There is no equivalent Composer and service-provider flow for Laravel, so nothing here plugs into a Laravel application without a rewrite.
- Is the new directory listing feature in 2.0 a security concern?
- It deserves scrutiny. A listing endpoint over upload storage is a classic information-disclosure and file-enumeration vector, and it widens the blast radius of any path-traversal or authorization defect in the upload path. The release note is a single line with no detail on scope, authorization or sandboxing, so the risk is unquantified. In an alpha package with no downstream users to surface defects, treat it as unreviewed and disable or audit it before considering adoption.
- What are the best alternatives to makinacorpus/filechunk-bundle for Laravel?
- For Laravel, building chunked uploads natively is usually cheaper than porting a Symfony bundle. Common options include S3 or Flysystem multipart uploads, a maintained Laravel chunk-upload package, tus-based resumable upload protocols, or Livewire file uploads with chunk configuration. That route keeps you on a maintained foundation with semver guarantees rather than an alpha dependency.
- Is makinacorpus/filechunk-bundle compatible with modern PHP 8 and Symfony 6 or 7?
- A major 2.0 bump from a 2019-era 1.x almost certainly drops PHP 5.6 and 7.x plus Symfony 2 and 3 constraints, but the release notes do not document a supported matrix. You should inspect composer.json in the alpha tag and run your own compatibility tests before assuming support. Because it is an alpha, the baseline can shift between releases without notice.
- Do I actually need chunked or resumable uploads, or is simple large-file upload enough?
- Start by validating the requirement before adopting any package. Often tuning upload_max_filesize and post_max_size in PHP and client_max_body_size in nginx is sufficient for large-file uploads. Chunking earns its complexity when files are very large, networks are flaky, or users need to resume interrupted transfers. If those conditions do not apply, a Symfony-only alpha upload component is a poor trade.
Weaver
How can I help you explore Laravel packages today?