- What is NativeKit v5 and how does it relate to NativePHP?
- NativeKit v5 is a Laravel starter kit for building native desktop and mobile applications with NativePHP, letting you keep a familiar Laravel workflow while packaging an app for native platforms. It ships a preconfigured Laravel plus NativePHP scaffold, a ready-to-use app layout with an authentication flow, and a Vite and Tailwind frontend setup. It also layers a native and mobile styled UI kit on top of a Filament v5 panel, which makes it a presentation-layer package rather than an infrastructure dependency.
- How do I install nativekitv5 with Composer?
- Install it with composer require jeffersongoncalves/nativekitv5 in a Laravel application that already runs Filament v5. After the install, run composer update and review the lockfile diff so you can see exactly which Filament and supporting package versions were resolved. Then follow the package documentation to publish its views and compiled assets and register the panel plugin. Because the asset pipeline is involved, verify the panel actually loads its CSS and JavaScript before moving on.
- Which Laravel, PHP and Filament versions does nativekitv5 support?
- The package requires Filament v5, and by implication the Laravel and Livewire versions that Filament v5 supports. The authoritative answer is always the php, laravel/framework and filament/filament constraints declared in the package composer.json, so check those before bumping your constraint. Do not assume a clean upgrade based on the package version number alone, because that number tracks Filament's release line rather than an independent schedule.
- Why does the nativekitv5 version number match Filament's version?
- The package version is re-baselined onto Filament's release line, so nativekitv5 5.10.1 corresponds to a newer Filament patch or minor line than 5.8.4. That means you cannot infer API stability from the package version alone, since a minor bump here may carry a Filament minor bump underneath it. Pin the version explicitly and read the changelog instead of relying on semver assumptions. Add the package to a watch list if you need predictable upgrade windows.
- How do I upgrade nativekitv5 from 5.8.4 to 5.10.1 safely?
- Treat it as at least a patch-level upgrade: bump the constraint, run composer update, and review the lockfile diff for the four composer dependency updates. Check which Filament version is resolved before and after the update, since the jump spans multiple minor lines. Rebuild or republish the compiled assets if the package does not ship prebuilt ones, then smoke-test panel asset loading and any customised theme or published view overrides. Automated tests plus a staging deploy will catch the usual UI-layer breakages.
- Do I need Node, pnpm and Vite to use nativekitv5?
- The package ships a real frontend build, registered through Filament's asset pipeline, and it manages overrides through pnpm-workspace.yaml. You only need a Node and pnpm toolchain if you rebuild the assets yourself or customise the Tailwind theme. If a release ships prebuilt compiled assets, your CI can skip Node entirely. Confirm whether the published assets are prebuilt before you add a build step to your pipeline.
- Should nativekitv5 be a production or a dev dependency?
- It belongs in require rather than require-dev, because it registers Filament assets, views and Livewire components at runtime. Architecturally it sits at the top of the stack as a presentation-layer plugin, consuming Filament's panel registration and Blade contracts. Nothing in your application domain code should ever depend on its classes directly, so keep any integration behind your own views and configuration.
- Can I use nativekitv5 with Filament v3 or v4?
- No. The package targets Filament v5, so a Filament v3 or v4 panel needs to be upgraded first. If your application does not run Filament at all, the UI layer is irrelevant to you and you would only be interested in the NativePHP scaffolding. Check the resolved Filament version in your lockfile before assuming compatibility.
- Are the shell-quote and source-map-js pnpm overrides a security concern?
- The release pins shell-quote and source-map-js through pnpm overrides instead of upgrading them directly, which fixes the package's own build graph but creates a latent staleness surface. Overrides are not tracked by Dependabot the way direct dependencies are, so those pins can silently fall behind upstream security fixes. Check whether the overrides correspond to published CVEs or to known-good pinning, and define an exit criterion for removing them. Either way, put it on a watch list rather than treating it as a blocker.
- What are the alternatives to nativekitv5?
- The closest alternatives are a plain Filament v5 panel with your own Tailwind theme, a general-purpose Filament starter kit, or wiring NativePHP directly into Laravel without a prebuilt UI kit. The trade-off is setup time versus control: starter kits save scaffolding work but add a dependency whose version tracks another package's release line. Evaluate the maintenance cadence, the declared composer constraints and the frontend build requirements before committing.