- What is torann/skosh and what does it do?
- Skosh is a Laravel package by Torann for generating static sites in PHP, using Gulp for the build workflow. It installs via Composer and integrates with Laravel's configuration and service container. It is a small, focused utility rather than a full CMS or opinionated site framework.
- How do I install torann/skosh in a Laravel application?
- Run composer require torann/skosh and let Laravel package auto-discovery register the service provider, or register it manually if your app disables discovery. Then publish the package config with php artisan vendor:publish and adjust the generated config. Ensure your build environment has Node.js and Gulp available because Skosh uses Gulp for its static-site build tasks.
- Does torann/skosh support Laravel 10, Laravel 11, and PHP 8.2?
- The package declares a PHP floor of 7.2+, which is permissive and does not conflict with Laravel 10/11's PHP 8.1/8.2 requirements. However, a 7.2 floor suggests the CI matrix may still target legacy PHP, so you should verify Skosh on your PHP 8.2 or 8.3 runtime before relying on it in production. It should install on modern Laravel, but treat it as untested-on-your-runtime until you confirm.
- How do I configure Skosh after installation?
- Publish the package configuration with Laravel's vendor:publish command, then edit the generated Skosh config file for your paths and build options. Because Skosh is a small utility, the config surface is likely limited; keep environment-specific values in .env where possible. If auto-discovery is disabled, register the Skosh service provider in config/app.php before publishing.
- What changed in Skosh 0.3.0 and is it a breaking change?
- The 0.3.0 release drops the Twitter plugin, adds coding standards, and includes a broad code cleanup. The Twitter plugin removal is the key risk: if it removed a public class, interface, config key, or service binding, it is an API break shipped in a pre-1.0 minor. Since the context provides no migration note or deprecation path, test carefully and pin to 0.2.* if you depend on that integration.
- Is the Twitter plugin still available in torann/skosh?
- No, the Twitter plugin was dropped in version 0.3.0. If your application relied on it, the safe path is to stay on 0.2.* until you confirm whether the removal was purely internal or a public API break. The release notes in the provided context do not include a replacement or migration guide, so audit your code for references before upgrading.
- How do I test torann/skosh in a Laravel project?
- Add the package to a test application and run your normal Laravel test suite against it, focusing on service provider registration, config publishing, and any generated static output. Because the package uses Gulp, include a build-environment test that verifies Node and Gulp tasks run in CI. Also run the suite on PHP 8.2/8.3, not just the declared 7.2 floor, to catch runtime differences.
- Is torann/skosh actively maintained and safe for production?
- The context shows a 0.3.0 release that trims scope by dropping the Twitter plugin and performs cleanup, which can indicate active curation or pre-abandonment. Pre-1.0 packages are allowed to break, but the lack of a detailed changelog and migration notes raises maintenance risk. For production, pin a version, review the diff, and verify test coverage and CI against modern PHP before adopting.
- Can I use Skosh without Gulp or outside Laravel?
- Skosh is described as a static site generator for PHP that uses Gulp, so Gulp is part of its intended build workflow; removing it likely means replacing the build pipeline yourself. It is also packaged as a Laravel package, so the documented integration path assumes Laravel's service container and config. Using it outside Laravel may be possible but is not the supported path in the provided context.
- What are alternatives to torann/skosh for static site generation in Laravel?
- Alternatives depend on whether you want a Laravel-native generator or a standalone PHP/Gulp workflow; common choices include Jigsaw, Sculpin, or a custom Laravel command plus a static-site build tool. If you need Laravel integration, evaluate packages that explicitly support Laravel 10/11 and PHP 8.2 with an active test matrix. Compare maintenance cadence, changelog quality, and whether the tool requires Node/Gulp before switching.