Weave Code
Krayin Package Generator Laravel Package
krayin/krayin-package-generator
A Laravel package generator for Krayin CRM that scaffolds new packages with boilerplate structure, service providers, configuration, and conventions, helping developers build and extend CRM features faster.
Krayin Package Generator
Frequently asked questions about Krayin Package Generator
- What is krayin/krayin-package-generator used for?
- It is a Laravel Artisan tool for scaffolding custom Krayin CRM extensions. It creates a PSR-4 compliant package skeleton with a composer.json, service provider, config, routes, migrations, and views so developers can start building CRM modules without boilerplate.
- How do I install krayin/krayin-package-generator?
- Install it with Composer in your Krayin or Laravel project, preferably as a dev-only dependency because it is development tooling rather than runtime code. After installation, run the package's Artisan generator command to scaffold a new module.
- Which Krayin, Laravel, and PHP versions does version 2.0.0 require?
- Version 2.0.0 explicitly tracks Krayin v2.0.0, so it is intended for teams on the Krayin 2.x line. The available context does not specify the exact Laravel and PHP minimum versions, so check the package composer.json and release notes before upgrading.
- Can I use Krayin Package Generator with Krayin 1.x?
- The v2.0.0 release aligns with Krayin v2.0.0, which implies a version-coupled pairing of generator 2.x with Krayin 2.x. Teams still on Krayin 1.x should remain on the prior generator line and should not assume that 2.x output is compatible with Krayin 1.x.
- What files does the generator create?
- It scaffolds a complete package skeleton, including composer.json, a service provider, configuration, routes, migrations, and views. It also includes publishable assets, language files, and view stubs, following Krayin and Laravel conventions for easy registration.
- Does it support non-interactive scaffolding in CI pipelines?
- The newer release adds interactive prompting when no arguments are passed, which can block automated or non-interactive execution. Confirm that full flag and argument invocation still works for CI and that the prompt behavior can be suppressed before relying on it in scripted scaffolding.
- Can I customize the generated package stubs for company conventions?
- The tool generates boilerplate from stubs, but the available context does not confirm how customizable those templates are. Teams should inspect the stubs, test output against internal standards, and consider forking or wrapping the generator in an internal starter kit for organization-specific conventions.
- Should krayin/krayin-package-generator be a production dependency?
- No, it should be treated as dev-only Artisan and Composer tooling for scaffolding Krayin modules. It belongs in the engineering workflow, not the runtime dependency graph of a production CRM application.
- Does it generate tests, migrations, permissions, UI assets, and translations?
- It generates migrations, views, publishable assets, and language files as part of the package skeleton. Tests and permissions are not confirmed in the provided context, so verify those outputs against your project requirements.
- What are alternatives to using this generator?
- Alternatives include hand-building a Krayin module skeleton, using generic Laravel package generators, or wrapping this tool in an internal starter kit with pinned versions and custom templates. For teams on Krayin 2.x, a time-boxed pilot that diffs generated output against a hand-built module is the safest evaluation.
Weaver
How can I help you explore Laravel packages today?