- How do I install and configure claudiodekker/word-generator in Laravel?
- Install it with composer require claudiodekker/word-generator. Laravel package auto-discovery registers the optional service provider and facade, so you can resolve the generator from the container without manual wiring. Commit any custom word lists or configuration to your application repository and review them like other application data.
- Does claudiodekker/word-generator work with Laravel 10, 11, and 12?
- Support depends on the Composer constraints of the release you install, so check the package's composer.json and repository history for the exact Laravel and PHP versions listed. Because the core is framework-agnostic and Laravel integration is optional, you can still use the generator directly in plain PHP if a Laravel integration release lags behind. Verify compatibility during a short spike before adding it to a production project.
- Can I use word-generator in plain PHP without Laravel?
- Yes. The package is framework-agnostic and can be instantiated directly in any PHP project, script, queue worker, or CI fixture tool. The Laravel service provider and facade are optional conveniences rather than requirements.
- How do I generate random sentences and paragraphs with this package?
- Use the fluent API to request words, then build sentences and paragraphs with configurable counts. It is designed for readable placeholder text rather than semantically meaningful prose. Wrap calls in your own helper if you need consistent formatting across views, seeders, or demo-data generators.
- Is word-generator suitable for database seeders and model factories?
- Yes, seeders and factories are a strong fit because generated words are readable and require no external service. Avoid assertions that depend on exact random output unless you replace values with fixtures. For identifiers or slugs, wrap the generator with uniqueness checks before persisting.
- Is claudiodekker/word-generator safe for passwords, API tokens, or security codes?
- No. The package generates random words from word lists, not cryptographically secure random values, so it is unsuitable for passwords, API tokens, security challenges, or any value requiring entropy or uniqueness guarantees. Use Laravel security helpers or a CSPRNG for those cases.
- How do I use custom word lists with word-generator?
- The package supports custom word lists, which is useful for localisation, domain-specific fixtures, or controlled placeholder vocabulary. Store lists in version control, assign an owner, and review them for content, profanity, and licensing before use. Treat custom lists as application data rather than throwaway configuration.
- How do I get deterministic or reproducible random words in tests?
- Random output is not guaranteed to be seedable, so avoid asserting exact generated words in tests. Wrap the package behind a small internal generator interface and substitute deterministic fixtures or a fake in tests. This also gives you one place to handle collisions and future replacement.
- Does word-generator guarantee unique slugs or human-readable identifiers?
- No. It produces random words but does not guarantee uniqueness, so slugs and identifiers can collide. Add database unique constraints plus retry, suffix, or hash strategies at the call site. Wrap generation in your own service if identifiers become a real use case.
- How does word-generator compare to Faker, and is it still maintained?
- Faker is broader fixture generation, while word-generator is narrower and focused on readable words and phrases, so they complement each other. Maintenance risk is moderate because it is a small single-maintainer package, but the framework-agnostic core makes replacement straightforward. Check release history and Composer constraints before relying on it across a new Laravel major version.