- How do I install caouecs/gumby2 in a Laravel 4 application?
- Require the package with Composer, then register Caouecs\Gumby2\Gumby2ServiceProvider in the providers array in app/config/app.php. Run php artisan asset:publish caouecs/gumby2 to expose the Gumby2 CSS, JavaScript, and Sass under public/packages/caouecs/gumby2. Finally include gumby.css and gumby.js in your master Blade layout. This only applies to a genuine Laravel 4 application on PHP 5.3 to 5.6.
- Does caouecs/gumby2 work with Laravel 8, 9, 10, or 11?
- No. The package targets Laravel 4 package conventions and will conflict with modern illuminate/support constraints, and the asset:publish command it relies on is not part of later Laravel releases. Installing it in a Laravel 8+ app is typically a Composer resolution failure, not a configuration issue. Modern stacks use Vite, package auto-discovery, and supported PHP versions.
- What Laravel and PHP versions are required for caouecs/gumby2?
- It is built for Laravel 4.x and expects PHP 5.3 through 5.6. Laravel 4 has been end-of-life since 2015, and PHP 5.x has been unsupported since 2018 and 2019. It cannot coexist with Laravel 5+ because of its illuminate/support 4.x constraint.
- How do I publish Gumby2 CSS and JavaScript assets in Laravel 4?
- After registering the service provider, run php artisan asset:publish caouecs/gumby2. The command copies the package assets into public/packages/caouecs/gumby2 so they can be served directly. Reference gumby.css and gumby.js from your Blade master layout. If you plan to edit Gumby's Sass source, account for the Compass build chain separately.
- Can I use Gumby2 Blade helpers for grids, buttons, and UI components?
- The package includes Blade helpers intended to make Gumby grid, button, and UI markup quicker to output, but they are thin conveniences over Gumby's CSS classes. They are not a full Blade component library, so most views will still contain Gumby-specific HTML and classes. Treat the helpers as optional sugar rather than a reason to adopt the package.
- Why does Composer fail when I require caouecs/gumby2 in a modern Laravel project?
- Composer fails because the package's constraints resolve to Laravel 4-era illuminate/support and an old PHP runtime. Modern Laravel applications require newer illuminate components and PHP 8+, so the dependency graph cannot be satisfied. The package also relies on Laravel 4 asset:publish conventions that later versions removed or changed. There is no supported compatibility shim.
- Is caouecs/gumby2 maintained and safe for production?
- It is effectively unmaintained: Laravel 4 and PHP 5 are EOL, Gumby2 is abandoned upstream, and its Compass and Ruby Sass toolchain is also EOL. The package has a single maintainer, about 10 stars, and no dependents, so there is no community triage or security response. Using it in new production work is high risk. It is only reasonable for containing an existing legacy Laravel 4 app.
- How do I migrate a Laravel app away from Gumby2?
- For legacy containment, publish the assets once, vendor them into public, and remove the runtime Composer dependency so the app no longer boots the service provider. For modernization, rebuild the UI on a maintained framework such as Bootstrap 5, Tailwind CSS, or an internal design system on Laravel 10 or 11 with Vite. Inventory Gumby class and mixin usage in Blade templates, migrate layouts first, then pages behind feature flags. Decommission the old asset pipeline and Compass from CI.
- Can I compile Gumby2 Sass with Dart Sass or Vite instead of Compass?
- Gumby2's Sass source depends on Compass-specific mixins such as span and respond, which do not compile under Dart Sass without a compatibility shim. Vite can process Sass, but it will not provide those Compass mixins automatically. If you only ship prebuilt gumby.css, you can avoid the Sass toolchain entirely. If you need to modify styles, budget for a Sass migration or a maintained replacement framework.
- What are the best alternatives to caouecs/gumby2 for Laravel front-end development?
- For a modern Laravel app, use a maintained CSS framework such as Bootstrap 5 or Tailwind CSS with Vite, or an internal design system. If you are locked into Gumby-specific markup, the realistic options are freezing the published assets or forking and owning the code. There is no drop-in Composer replacement for Laravel 5+ that preserves Gumby2's Laravel 4 helpers. Choose based on whether the goal is legacy containment or migration to a supported stack.