- What is regularjack/frontend-bundle and what does it do in a Laravel app?
- It is a Composer package that gives Laravel applications a ready-made frontend layer: publishable Blade components, layouts and partials, preconfigured Vite and Tailwind asset publishing, configurable theme tokens and CSS variables, and Artisan commands for scaffolding and cache clearing. It sits at the build/asset-compilation layer rather than in the request lifecycle, so nothing in your domain logic or HTTP layer depends on it. That low coupling makes it easy to replace, which is exactly why it is replaceable rather than defensible.
- Is regularjack/frontend-bundle still maintained or is it deprecated?
- It is deprecated. The v0.2.2 release contains no functional change at all; its entire content is a deprecation notice redirecting users to Webpack Encore. Treat abandonment risk as certain rather than probable, because deprecation is a declared end state, not a warning signal. Upstream fixes for future PHP, Laravel and Node compatibility will not arrive.
- How do I install regularjack/frontend-bundle with Composer?
- The normal path is a Composer require into a Laravel project followed by publishing the package's Blade and asset resources, then wiring the Vite build into your templates. Be aware that installing it today means adopting a package that is already end-of-life, so the cost of adoption immediately includes the cost of a later removal. For anything greenfield or actively developed, prefer the stated successor, Webpack Encore, from day one.
- Which Laravel and PHP versions does regularjack/frontend-bundle support?
- The package targets modern Laravel releases and PHP 8.1 and above. The important caveat is that this support matrix is frozen: the deprecated package will not track future Laravel major versions or new PHP releases. That turns a routine framework upgrade into a migration project on a timeline you do not control.
- How does the bundle publish Blade components, layouts, and partials?
- It ships publishable Blade components, layouts and partials so you can compose UI from consistent, reusable pieces instead of hand-writing view partials. Published files land in your application's view directories and become yours to maintain. Once published, any per-component conventions you build on top of them are part of your migration surface if you later move to another tool.
- How does Vite and Tailwind configuration work in this bundle?
- The bundle provides zero-config Vite and Tailwind asset publishing, plus configurable theme tokens exposed as CSS variables. In practice this means the build tooling and design tokens are wired for you rather than assembled by hand. Note that this Vite/Tailwind orientation differs from the package's own deprecation notice, which points users to Webpack Encore, so verify your target stack before committing.
- What should I do if my Laravel app already uses regularjack/frontend-bundle?
- Inventory first: confirm which production and staging codebases reference it, and pin the exact Laravel, PHP and Node versions each is built against. Then size the migration by counting build configurations, CI jobs and developer runbooks that mention it, and check whether any custom asset conventions or plugins sit on top that Encore does not cover natively. Treat the move as planned technical debt retirement rather than an emergency, but do schedule it.
- What is the alternative to regularjack/frontend-bundle now that it is deprecated?
- The package's own deprecation notice redirects users to Webpack Encore, a Symfony-originated tool with a broader and more actively maintained footprint. Encore is a well-trodden path for PHP applications generally and keeps you on a supported branch, which also reduces exposure to Laravel-specific frontend churn. If Encore does not suit your stack, choose an actively maintained asset pipeline rather than a frozen one.
- How do I test that asset builds still work after migrating off the bundle?
- Freeze the blast radius by pinning current versions, then stand up the replacement pipeline and run both builds against the same source assets for comparison. Check the failure mode explicitly: does a broken build block deployment, or do degraded assets ship silently? Silent degradation is the classic risk with deprecated build tooling, because it often keeps working for quarters and then fails during an unrelated upgrade or a CI runner image change.
- Can I use regularjack/frontend-bundle in a new production Laravel project?
- It is not recommended for greenfield or actively developed codebases. The only defensible narrow case is a short-lived, low-traffic internal tool with a hard delivery date where the asset pipeline is not a differentiating concern and the team explicitly accepts a one-way door. Even then, the successor tool is the better choice, since adoption cost now includes a knowable but non-trivial removal cost later.