Weave Code
Core Laravel Package
cms-orbit/core
CMS Orbit Core is a modular Laravel CMS foundation with flexible content types, a clean admin layer, and extensible APIs. Build and manage sites quickly with reusable fields, routing, and publishing tools designed for custom PHP applications.
At a glance
Frequently asked questions about Core
- What is cms-orbit/core used for in a Laravel application?
- cms-orbit/core is a modular Laravel CMS foundation that provides flexible content types, a clean admin layer, routing, publishing tools, and extensible APIs. It is designed for custom PHP applications that need CMS and domain logic plus TypeScript frontend tooling. It also includes an orbit:frontend-sync command for generating or updating tsconfig.json path aliases.
- How do I install cms-orbit/core in a Laravel project?
- Install it with Composer using composer require cms-orbit/core. After installation, run php artisan orbit:frontend-sync to generate or update the TypeScript path aliases used by @cms-orbit/core imports. The 4.6.2 patch notes do not mention database migrations, but you should still review the package documentation for any standard Laravel package registration steps.
- Which Laravel and PHP versions does cms-orbit/core support?
- The 4.6.2 release was tested on PHP 8.4 and 8.5, while older PHP versions are unverified in this release. The provided context does not list exact Laravel framework version constraints, so check the package composer.json for the official laravel/framework requirement. Pin the version and test it in your application before upgrading.
- How do I run the orbit:frontend-sync command?
- Run php artisan orbit:frontend-sync from your Laravel application root after installing or updating the package. The command generates or updates tsconfig.json path aliases, which helps custom components import from @cms-orbit/core. Review the resulting tsconfig diff before committing, especially in projects with custom TypeScript configuration.
- Why did orbit:frontend-sync not update my tsconfig.json paths?
- The command has a known manual step for tsconfig.json files that contain comments; in that case you must apply the generated paths by hand. Also confirm the command ran in the correct application root and that your tsconfig does not use complex extends or project references that the command does not handle. Compare the command output with your tsconfig.json to see which aliases were missed.
- Does cms-orbit/core work with Laravel Octane?
- laravel/octane is declared as an optional suggestion in cms-orbit/core, so Composer can surface it to Octane users. The package shows awareness of high-concurrency deployments, but this release does not prove Octane compatibility or confirm that Octane is exercised in CI. Validate the package under Octane in your own environment before relying on it in production.
- How do I test custom component imports from @cms-orbit/core after updating?
- Run php artisan orbit:frontend-sync, then run your TypeScript type-check and frontend build to verify module resolution. Specifically test direct imports from @cms-orbit/core and any custom component registration paths. The 4.6.2 fix addresses bare-alias generation for packages that expose index.ts, index.tsx, or index.js, so those imports should be part of your validation.
- What changed in cms-orbit/core 4.6.2?
- Version 4.6.2 fixes issue #9, where bare-alias generation missed packages exposing index.ts, index.tsx, or index.js, causing TypeScript module-resolution failures for direct imports. It also correctly declares the optional laravel/octane suggestion in Composer. This is a patch-level update with no database migrations or breaking API changes noted, but it does change generated tsconfig output for affected packages.
- Is cms-orbit/core actively maintained and does it follow semver?
- cms-orbit/core has active patch releases, but release notes are primarily in Korean and branch hygiene has been inconsistent. The 4.6.1 release history was on a separate branch and merged late, and a missing suggest entry was only corrected in 4.6.2. The package uses patch-style versioning, but teams should track tags, pin versions in composer.json, and review patch diffs rather than assuming every release is cleanly managed.
- How should I deploy a cms-orbit/core update to production?
- Update in a development branch, run composer update cms-orbit/core, then run php artisan orbit:frontend-sync and inspect the tsconfig.json diff. Run frontend type-check and build plus backend tests, and validate imports from @cms-orbit/core and custom component registration. Deploy to staging first, and avoid regenerating TypeScript config directly in production without reviewing the diff.
Weaver
How can I help you explore Laravel packages today?