- What does the laravel-frontend-presets/zurb-foundation package do?
- It is a Laravel frontend scaffolding installer that replaces the default Bootstrap 4 frontend with Zurb Foundation. When its preset command runs, it overwrites files such as package.json, webpack.mix.js, SCSS assets, layouts, and authentication views. It has no runtime API, facade, or meaningful config file.
- Which Laravel versions does laravel-frontend-presets/zurb-foundation support?
- Version 2.1.2 widens Composer constraints so the package can install on Laravel 6 through 11 and beyond. Functional support remains Laravel 5.5 through 5.8 because the php artisan preset command was removed in Laravel 6. A successful composer require does not mean the preset can actually run.
- Why is php artisan preset foundation not working after installation?
- Laravel 6 removed the php artisan preset command, and this package does not restore it. The v2.1.2 release only updated Composer metadata for newer Laravel versions. On Laravel 6 and later you may get a clean install but no working preset command.
- Can I use this package with Laravel 10 or Laravel 11?
- It may install on Laravel 10 or 11 because the illuminate/support constraints are open-ended, but it cannot function there. The preset entry point no longer exists, and the package has no Vite or modern Sass support. It is not recommended for current Laravel applications.
- Does this package support Vite or Laravel Mix?
- It targets the older Laravel Mix and Webpack pipeline, not Vite. It writes webpack.mix.js and the legacy resources/assets frontend structure. Modern Laravel defaults to Vite, so the scaffolding diverges from current conventions and would need manual migration.
- What files does the Zurb Foundation preset publish or overwrite?
- It overwrites the frontend baseline, including package.json, webpack.mix.js, resources/assets/sass files, resources/views/layouts, and the authentication views. The result is Foundation markup and its SCSS/JS pipeline instead of Bootstrap 4. Back up or commit your app before running any scaffolding preset.
- Is laravel-frontend-presets/zurb-foundation actively maintained?
- There has been one release since May 2020, and v2.1.2 is a metadata-only constraint widening with no functional changes. The project has low stars and no known dependents exercising the code. Treat it as legacy or abandoned rather than actively maintained.
- What are alternatives to this package for using Foundation in Laravel?
- Because Laravel removed the preset mechanism, the safer alternative is to install Foundation manually with npm and configure Vite or Mix yourself. You can also use maintained frontend presets for Tailwind or Bootstrap. Choose manual scaffolding if you have a real Foundation design-system requirement.
- Will this package build on modern Node.js or CI images?
- It pins an old Foundation for Sites 6.x release, jQuery, and node-sass-based tooling. node-sass is deprecated and often fails on Node 16 and newer without workarounds. Build reproducibility on modern CI images is poor, so expect dependency upgrades and manual fixes.
- Is it safe to use laravel-frontend-presets/zurb-foundation in production?
- Technical risk is high because the frontend dependency tree is unpatched and the package has no real maintenance cadence. The worst failure mode is install-succeeds but command-absent on modern Laravel, which can mislead teams into thinking it is supported. Use it only for legacy Laravel 5.5–5.8 projects with a clear Foundation mandate and a plan to maintain the assets.