- What is neuralglitch/omnia-ipsum used for?
- Omnia Ipsum is a fake-content generator for placeholder text, images, audio and video. It bundles Lorem Ipsum generators, third-party image and media URL providers, and FakerPHP passthrough helpers. It is aimed at development, seeding, demos and test data rather than production runtime code.
- Is Omnia Ipsum a Laravel package or a Symfony package?
- Despite being described as a Laravel package, the documented integration surface is Symfony and Twig: 12 Twig functions, a Symfony Flex recipe, and Symfony 6.4, 7.x and 8.x compatibility. There is no Laravel service provider, Blade integration or publishable Laravel config. The underlying generators are likely plain PHP classes, so Laravel use is feasible but requires a thin adapter.
- How do I install Omnia Ipsum in a Laravel application?
- You can add neuralglitch/omnia-ipsum as a require-dev Composer dependency, but there is no Laravel service provider or config/omnia.php publish tag yet. In practice you would need a wrapper package to bind configuration and expose Blade helpers. The vendor package is Symfony-first through Flex and Twig, so plain installation will not give you Laravel-native integration.
- Does Omnia Ipsum support Laravel 10, 11 and 12?
- There is no published Laravel version matrix. Symfony 6.4, 7.x and 8.x support implies PHP 8.1+, which lines up with Laravel 10, 11 and 12 in principle. Treat Laravel compatibility as unproven and verify the composer.json PHP constraint before adopting it.
- Are there Blade directives for Omnia Ipsum?
- No, the package documents 12 Twig functions and a Symfony Flex recipe rather than Blade directives. There are no @omniaImage, @omniaAvatar or @lorem helpers, and no Laravel config publish tag. A Laravel wrapper would need to mirror the Twig functions one-to-one.
- Can I use Omnia Ipsum in Laravel seeders and factories?
- It fits the same require-dev slot as FakerPHP for seeders, factories, staging fixtures and demo environments. Its unique value is media placeholders such as avatars, images, video and audio URLs. Text generation mostly overlaps with Faker, and you must namespace its fake() helper to avoid collisions.
- Does Omnia Ipsum make external network requests?
- Yes, every image, video and audio helper resolves to a third-party URL, including Picsum, Placehold.co, DummyImage, UI Avatars, SoundHelix and a Google Cloud Storage bucket. That means CI, demo and test environments will make outbound requests and depend on provider uptime. No offline mode is confirmed, so plan egress policy and mock or cache responses where needed.
- Will Omnia Ipsum's fake() helper conflict with Laravel's fake() helper?
- Yes, the package exposes fake() and fake_text() passthroughs to FakerPHP. Laravel 9+ already ships a global fake() helper, so importing the package helper into the global scope would collide. Namespace it or call it only through your own adapter layer.
- Is Omnia Ipsum stable enough for production?
- It is pre-1.0 at version 0.1.0, so there is no API stability guarantee and breaking changes are likely before 1.0. It is development and demo tooling, so it should stay in require-dev and never sit on a production request path. The technical risk is low to moderate overall, with most of it concentrated in external media providers.
- Are the placeholder video and audio assets safe to use?
- The 13 hosted video clips include Blender Foundation open content such as Big Buck Bunny, Sintel and Elephants Dream, but you should verify attribution terms. Audio is generated through SoundHelix, and all media URLs are external. Confirm the Google Cloud Storage bucket is a stable, non-temporary host, or mirror the assets internally.