- Is planmylife/front-bundle a Laravel package or a Symfony bundle?
- It is a Symfony bundle, not a Laravel package. The name suffix Bundle, the dependency-injection extension conventions, and the description all point to Symfony, and the package blurb explicitly targets Symfony-based projects. Laravel's package discovery, service container, and facade patterns are not part of its design.
- Can I install planmylife/front-bundle in a Laravel application?
- You can technically add it with Composer, but it is not a stack fit. Laravel's supported front-end path is Vite through laravel-vite-plugin, and pulling in a Symfony bundle plus a gulp pipeline leaves you maintaining two build systems and an unsupported integration surface. For a Laravel app the sensible answer is to skip this package entirely.
- What does planmylife/front-bundle actually do?
- The stated purpose is to generate the front end with gulp, and the blurb says it packages shared UI assets, templates, and presentation helpers for PHP applications. What is not clear from the description is whether it shells out to gulp, ships its own gulp configuration, or only scaffolds starter files. Those three possibilities imply very different integration costs, so read the source before assuming behavior.
- Do I need Node.js, npm, and gulp installed to use this bundle?
- Very likely yes. composer require alone will almost certainly not be enough, because the package embeds a Node and gulp build pipeline, so a working install probably needs Node LTS, npm, and a specific gulp major version present in the build environment. Confirm the expected gulp version and any asset source and output layout before wiring it into CI.
- Is planmylife/front-bundle maintained or abandoned?
- There is no meaningful adoption signal: zero stars, a zero score, and zero dependents. That pattern usually indicates a personal or internal project published publicly with no external testing, no issue history, and no evidence of a release cadence or security review. Treat it as a near-zero-signal dependency and assume you would be the first real consumer.
- Does planmylife/front-bundle run shell commands during composer install?
- The description does not say, so this must be verified in composer.json and any shipped scripts. If it registers post-install-cmd or post-update-cmd hooks that invoke gulp or npm, that may conflict with your CI security policy around network access and command execution. Check for those hooks before adding the package to any pipeline.
- What are the alternatives to a gulp-based front-end bundle in Laravel and Symfony?
- In Laravel, use laravel-vite-plugin with Vite, which is the first-party supported path and needs no PHP wrapper. In Symfony, symfony/webpack-encore or symfony/asset-mapper cover the same ground with maintained, first-party tooling. For any stack, if the real need is just running gulp, put a package.json and gulpfile in the application repository rather than depending on a PHP wrapper.
- Does planmylife/front-bundle support the PHP and framework versions I use?
- No framework constraint for Laravel exists, because this is a Symfony bundle, so there is nothing to match against your Laravel version. You still need to check the declared PHP constraint and the Symfony major version against your runtime, and verify Node LTS availability in your CI images. Also confirm the bundle does not assert an asset directory layout that conflicts with your existing structure.
- How do I safely fork or vendor planmylife/front-bundle if I really need it?
- Do not depend on upstream directly. Fork it into an internal namespace, pin the exact commit, and treat upstream as a one-time source extraction rather than a live dependency. Wrap the build step behind your own Composer script or Make target so the bundle stays replaceable, and define exit criteria in advance, for example taking ownership if there is no upstream commit in six months or gulp moves to a new major version.
- What license does planmylife/front-bundle use, and can I redistribute it?
- The license terms are unverified from the available information, so check the LICENSE file and the license field in composer.json before any commitment. Redistribution and forking rights depend entirely on that answer, and there is no stated support model behind the package. Resolve this before vendoring it into an internal namespace.