- How do I install sukei/bsod-bundle with Composer?
- Run composer require sukei/bsod-bundle from your project root. Then register the bundle in your Symfony application's bundle configuration. Because it is a Symfony bundle, Laravel projects cannot install and use it without custom integration.
- Does sukei/bsod-bundle work with Laravel?
- It is built as a Symfony bundle, so there is no official Laravel support. Laravel developers would need to adapt the BSOD rendering logic into Laravel's exception handler. For Laravel error pages, use Laravel-focused tools such as Ignition or Whoops instead.
- Which Symfony versions are compatible with sukei/bsod-bundle?
- Compatibility depends on the package's composer.json constraints and the Symfony version you run. Check the Packagist page and repository for supported Symfony releases before installing. Test in a branch if you are upgrading a major Symfony version.
- How do I configure the Blue Screen of Death error page?
- Register the bundle and follow its README configuration for enabling the BSOD exception renderer. The package is designed to replace standard exception output with Windows-style crash visuals in development. Keep configuration minimal until you confirm it renders as expected.
- Can I use sukei/bsod-bundle in production?
- This bundle is intended for development and debugging, not production error handling. Exposing detailed crash-style pages can reveal sensitive information to users. Enable it only in dev or local environments and keep production error pages generic.
- How do I enable the BSOD page only in the dev environment?
- Register or load the bundle only in your dev configuration, or conditionally add it based on the Symfony environment. Confirm that debug mode is enabled in dev so exceptions are rendered. Do not load the bundle in production bundle configuration.
- How can I customize the BSOD screen text or layout?
- Customization depends on the bundle's configuration and templates, so check the README for available options. The core behavior is to convert exceptions into a Windows BSOD-style page. If no options exist, you may need to override templates in your app.
- Is sukei/bsod-bundle actively maintained?
- Check the GitHub repository for recent commits, releases, and open issues before adopting it. Also review Packagist release history and Composer constraints. Because it is a novelty dev tool, pin a version that works with your Symfony app.
- What are alternatives to sukei/bsod-bundle for error pages?
- Symfony's built-in exception page and the profiler are the standard development alternatives. Laravel developers often use Ignition or Whoops for detailed error screens. The BSOD bundle is mainly for nostalgic Windows-style visuals rather than deeper debugging features.
- How do I test that the BSOD error page is working?
- Trigger an exception in a dev route or controller, for example by throwing a RuntimeException. Make sure the bundle is registered in dev and the cache is cleared. The response should show the Windows BSOD-style error page instead of the default Symfony exception screen.