- Is lake/larke-admin-frontend a Laravel PHP package I can install with Composer?
- No. Despite the Composer package name, lake/larke-admin-frontend is a Vue 2 and Element-UI single-page application, not a PHP package. It is the companion admin UI for the larke-admin Laravel backend. You build it with a Node toolchain and deploy static assets, while the PHP code lives in larke-admin.
- What Laravel versions does larke-admin-frontend support?
- Laravel version support is inherited from the larke-admin backend, not this frontend repository. The frontend must be pointed at a running larke-admin API. Validate PHP and Laravel compatibility against the backend documentation and your own baseline before adopting it.
- How do I install and build larke-admin-frontend?
- Install the Node dependencies, build the Vue 2 app with the project's webpack and babel-era tooling, and deploy the generated static assets. Pin your Node version and commit lockfiles because the build stack is dated. You also need a running larke-admin backend API for the UI to function.
- Do I need the larke-admin backend to use this frontend?
- Yes, in practice. The frontend has no headless or standalone mode and exists to serve larke-admin. It only has architectural value as a pair with the backend. Adopting it means adopting larke-admin's conventions and release cadence too.
- Can I use larke-admin-frontend with Filament or Laravel Nova?
- No. larke-admin-frontend is tied to the larke-admin backend API and its conventions. Filament and Laravel Nova are separate admin frameworks with their own frontends. You cannot use this UI as a drop-in frontend for those alternatives.
- Is Vue 2 and Element-UI still supported for larke-admin-frontend?
- Vue 2 reached end-of-life on 31 December 2023, and Element-UI is deprecated in favor of Element Plus. Neither receives security patches, so this frontend runs on an unsupported runtime. Treat it as a disposable shell and plan a Vue 3 and Element Plus migration if you adopt it.
- How do I customize the admin panel UI in larke-admin-frontend?
- Customize the Vue 2 source and rebuild, or replace views within the existing Element-UI structure. The UI is a conventional SPA, but there is no published component library or stable extension contract beyond what ships in the repo. Preserve the backend API contract so the UI can be replaced cheaply later.
- Does larke-admin-frontend include authentication and permission controls?
- The frontend bundles authentication screens and permission-aware navigation assets as part of the admin UI. Actual authentication and permission enforcement belong to the larke-admin backend. Test both sides of the API contract, because the repositories ship together and downstream validation is limited.
- What are alternatives to larke-admin-frontend for Laravel admin panels?
- Consider Filament with Livewire and PHP, Laravel Nova as a commercial supported option, or a bespoke Vue 3 and Element Plus SPA. Each avoids a deprecated UI runtime. Only choose larke-admin-frontend if you have already committed to larke-admin as your backend.
- Is larke-admin-frontend maintained and production-ready?
- Maintenance signals are weak: the repository has about 87 stars and zero dependents, providing little ecosystem validation. The paired backend's maintenance and release cadence determine whether this frontend stays viable. For production, audit dependencies, commit lockfiles, and budget for migration off Vue 2.