Weave Code
Angular Js Bundle Laravel Package
rhapsody-project/angular-js-bundle
Symfony bundle that packages AngularJS assets for easy inclusion in Symfony applications. It provides the AngularJS library through the bundle’s asset structure, helping teams add AngularJS front-end components without manually managing vendor files.
Symfony 2 bundle for AngularJS
Frequently asked questions about Angular Js Bundle
- What is rhapsody-project/angular-js-bundle used for?
- It is a Symfony bundle that ships the AngularJS JavaScript library as bundled assets so you can include Angular in your Symfony front end without hand-managing vendor files. It is aimed at legacy Symfony projects that still use AngularJS for client-side interactivity. The bundle keeps vendor JavaScript separate from your application code and works with Assetic-style asset management.
- How do I install rhapsody-project/angular-js-bundle with Composer?
- Install it with Composer using the package name rhapsody-project/angular-js-bundle from your project root. Composer will place the bundle under your vendor directory along with its packaged AngularJS assets. Check the repository README and composer.json for the exact version constraint and any required dependencies before installing.
- How do I register the AngularJSBundle in a Symfony application?
- Registration follows the normal Symfony bundle workflow. On older Symfony versions you add the bundle to the registerBundles() method in AppKernel.php; on Symfony 4 and later you add it to config/bundles.php. After registration, reference the bundle's assets from your templates or asset configuration.
- Which version of AngularJS does this bundle package?
- The bundle packages the AngularJS library, which is the original 1.x line of the framework rather than Angular 2 and later. The exact bundled version is determined by the package release you install, so verify it in the repository or the bundle's asset directory if you need a specific patch level. AngularJS is end-of-life upstream, so it is a maintenance choice rather than a forward-looking one.
- Does this bundle work with Assetic?
- Yes, it is designed to be compatible with Assetic-style asset management, which was the standard in older Symfony applications. You can reference the bundle's JavaScript assets in your Assetic configuration or directly in templates. If your project has moved to Webpack Encore or Symfony AssetMapper, you would typically install AngularJS through npm instead.
- Where are the AngularJS assets located after installation?
- The assets are shipped inside the bundle, typically under its Resources/public directory, which is the conventional location for Symfony bundle assets. You can reference them with the bundle-relative asset path in your templates, or publish them with the assets:install command on older Symfony versions. This keeps the vendor library out of your own source tree.
- Is rhapsody-project/angular-js-bundle compatible with Laravel?
- No. It is a Symfony bundle built around Symfony's bundle registration and asset conventions, so it cannot be used as a Laravel package. Laravel projects would instead pull AngularJS in through npm or a CDN link. The bundle exists specifically to support Symfony applications already committed to AngularJS.
- Which Symfony and PHP versions does this bundle support?
- The bundle targets legacy Symfony applications, so its supported Symfony and PHP ranges are usually narrower than current releases. Always read the require section of the package's composer.json to confirm compatibility with your Symfony and PHP versions. If you are on a recent Symfony release, running a modern asset toolchain is usually the better fit.
- Can I use this bundle instead of npm for managing AngularJS in Symfony?
- Yes, that is exactly its purpose: providing AngularJS as a Composer-managed Symfony bundle asset rather than an npm dependency. This suits older projects that never adopted a Node build step and rely on Assetic or direct script includes. Newer projects with Webpack Encore or AssetMapper will get better results from npm or yarn.
- Is this bundle actively maintained, and is it safe for production?
- It is part of the Rhapsody Project and is intended for legacy Symfony applications that still depend on AngularJS, so it should be treated as a maintenance-oriented package rather than an actively evolving one. Review the repository's recent commit activity and issue tracker before adopting it. Because AngularJS itself is end of life, plan a migration path to a supported front-end framework for long-term projects.
Weaver
How can I help you explore Laravel packages today?