- How do I install laravelangular/generators in a Laravel project?
- Install it with Composer using composer require laravelangular/generators, pin an explicit version, and register the package service provider if your Laravel version does not support auto-discovery. Then run php artisan list to confirm the generator commands are available. Validate the package Composer constraints against your PHP and Laravel versions before installing, because this is a legacy package.
- Which Laravel and PHP versions does laravelangular/generators support?
- It targets legacy Laravel monoliths with AngularJS 1.x front ends, not current Laravel releases. Expect incompatibility with modern PHP and Laravel versions, so check the Composer constraints and run a sandbox install first. Do not assume support just because Composer resolves it.
- What Artisan commands does laravelangular/generators provide?
- The package provides Artisan-powered generators for AngularJS building blocks such as components and services, plus full-stack CRUD scaffolding that can include models, migrations, controllers, routes, and Angular views. Exact command names and options depend on the installed version, so run php artisan list after installation. Treat the output as boilerplate to review, not production-ready code.
- Does laravelangular/generators work with Angular 2+ or only AngularJS 1.x?
- It is for AngularJS 1.x only and does not generate Angular 2+ or modern Angular code. The templates and directory conventions assume an AngularJS SPA alongside a Laravel backend. For new Angular work, use the Angular CLI instead.
- Why does 2.0.0 generate ES6 and do I need Babel or Webpack?
- Version 2.0.0 templates emit ECMAScript 6, so generated files need a transpilation step such as Babel with Webpack or Gulp before browser delivery. If your AngularJS app uses plain ES5 assets with no build pipeline, either stay on the pre-2.0 line or vendor and adjust the templates. Validate that the ES6 output transpiles and lints cleanly under your existing toolchain.
- What breaking changes are in laravelangular/generators 2.0.0?
- 2.0.0 is a major release that changes template output to ES6 and changes file extension consistency, which can break scripts, globs, IDE file templates, and CI checks. It is not a drop-in upgrade for teams that depended on the previous extensions. Generate sample files in an isolated branch and diff them against your conventions before upgrading.
- Can I customize the stubs used by laravelangular/generators?
- Yes, the package is designed with customizable stubs so generated files can match your project conventions. In practice, because the package is effectively unmaintained, the safer approach is to vendor or fork only the templates you need and adapt them internally. Avoid patching the dependency in place unless you can own that fork.
- Is laravelangular/generators maintained or abandoned?
- It is effectively abandoned: the prior release dates to 2016, AngularJS is end-of-life, and the package has zero dependents and a low score. The 2.0.0 release appears to be a one-off community contribution rather than a maintained revival. Treat it as a tactical scaffolding accelerator for a constrained legacy stack, not a strategic dependency.
- Can I commit generated files and remove laravelangular/generators from production?
- Yes, generated files are normal application code, so you can review, commit, and test them in your existing test suite, then remove the generator package from the dependency list. Keeping generated code committed avoids relying on an abandoned package in production or CI. Document the generation step and pin or vendor templates if you need reproducible output later.
- What are alternatives to laravelangular/generators for a new Laravel project?
- For a new Laravel project, do not adopt this package; use a modern frontend stack with Laravel and that framework's native CLI generators. If you must stay on AngularJS 1.x, prefer an internal Artisan generator or vendored templates over an abandoned Composer package. For existing legacy apps, migrate the frontend separately and set a retirement point for this tooling.