- What is sala/framework used for?
- Sala Framework is a Laravel/PHP package that provides a structured foundation for application development, including reusable conventions and Laravel-friendly integrations. It is distributed via Composer and can be used as a project starting point through composer create-project sala/framework. The provided material does not list every feature, so review the repository documentation before adopting it.
- How do I install sala/framework in a Laravel project?
- Use Composer, with composer create-project sala/framework as the documented entry point for a new project. For an existing app, add the package only after checking Packagist and the repository for the current package name, because v1.2.0 renames salaab/framework to sala/framework. Run your test suite immediately after installation to catch namespace or configuration issues.
- Does v1.2.0 break existing installations that use salaab/framework?
- Yes, a Composer vendor/package rename is a breaking change even though it ships as v1.2.0. The assessment notes that Composer and Packagist do not redirect renamed packages, so composer.json files pinned to salaab/framework may fail to resolve after the rename. The release notes described in the context do not mention a replace declaration, metapackage, or abandonment flag, so verify Packagist before upgrading.
- Did the PHP namespace change from Salaab to Sala?
- The provided assessment says the release renames composer.json and package.json identifiers, but it does not confirm whether the PSR-4 namespace changed. If the namespace moved from Salaab to Sala, every use statement, service provider reference, and published config tag in downstream code may need updating. Check composer.json autoload settings and the package source before migrating.
- Which Laravel and PHP versions does sala/framework support?
- The supplied material does not include the supported PHP/Laravel version matrix for v1.2.0. It only identifies PHP 8.x and Laravel on Composer as the primary surface and notes that CI enforcement is an open question. Check the package composer.json constraints and CI configuration before choosing it for a production app.
- How do I publish or configure Sala Framework settings?
- The context does not list configuration file names, publish tags, or service provider details for Sala Framework. Because the v1.2.0 notes may have changed identifiers, confirm the publish command and config keys from the repository documentation or vendor files. Do not assume old Salaab publish tags still work until you verify them.
- Is @salasolucoes/mcp required to run Sala Framework?
- @salasolucoes/mcp is described as an npm-distributed companion that implies a Model Context Protocol server for developer and AI tooling integration. The assessment does not establish whether it is optional or required at runtime for the framework. Review the framework composer.json and npm dependency declarations, and treat MCP as a separate tooling concern unless the docs say otherwise.
- What are the production risks of using sala/framework?
- The main risks in the assessment are the vendor rename without a documented Composer migration path, an unverified PHP namespace move, and very generic vendor names that raise supply-chain and typosquatting concerns. The package also now depends on external sala/console and @salasolucoes/mcp artifacts rather than local paths. Pin versions, verify Packagist ownership, and test upgrades in a branch before production rollout.
- Why is findProjectRoot a concern in Sala Framework and sala/console?
- The assessment describes a universal findProjectRoot heuristic with a SALA_PROJECT_ROOT override, mirrored in both the framework and console. Filesystem-walking project detection can fail in monorepos, nested projects, vendor directories, CI checkouts, and container mounts. Two duplicate implementations can also drift, so test those environments explicitly.
- What alternatives should I consider to sala/framework?
- The provided context does not benchmark alternatives, so compare it with Laravel starter kits or your own application skeleton if you mainly need scaffolding. Choose Sala Framework only if its reusable conventions and Laravel integrations match your team's needs. Weigh the v1.2.0 rename and dependency changes before adopting it over a simpler Laravel setup.