Weave Code
Backbone Js Bundle Laravel Package
rhapsody-project/backbone-js-bundle
Rhapsody Project's Symfony bundle for integrating Backbone.js into PHP applications. It packages the Backbone front-end library for easier asset management and configuration, helping teams add structured JavaScript MVC to Symfony projects with less manual setup.
BackboneJS Bundle for Symfony 2
Frequently asked questions about Backbone Js Bundle
- Is rhapsody-project/backbone-js-bundle a Laravel package?
- No. It is a Symfony bundle that packages Backbone.js and Underscore.js assets for Symfony asset workflows. Laravel does not natively support Symfony bundles, so you would install it with Composer only as a source of pinned JavaScript files. In a Laravel app you must copy or publish the assets yourself and wire them into Vite or your layout manually.
- How do I install Backbone.js in Laravel with Composer?
- Run composer require rhapsody-project/backbone-js-bundle, then copy the bundled Backbone and Underscore files from vendor into resources/js/vendor. Import them through your Vite entry point rather than referencing vendor paths at runtime. There is no Laravel service provider or auto-discovery, so the PHP glue will not register in Laravel.
- Which Backbone.js and Underscore.js versions does this bundle include?
- The 1.2 release bundles Backbone.js 1.2 with Underscore.js 1.6. The release note describes a front-end asset bump, not a PHP-side behavior change. Both libraries are old, so treat the pair as a pinned legacy dependency rather than a maintained modern stack.
- Does this package work with Laravel 10 or 11 and Vite?
- It can work only as a source of static JavaScript files. The package ships Backbone and Underscore assets but has no Vite plugin, Laravel service provider, or Blade directives. You must copy the files into resources/js, import them through Vite, and handle jQuery and dependency order yourself.
- Is Underscore.js 1.6 vulnerable to CVE-2021-23358?
- Yes. Underscore versions below 1.12.1 are affected by the _.template code-injection advisory tracked as CVE-2021-23358. Even if your application does not use _.template, software composition analysis scanners will flag the bundled 1.6 release. Plan to upgrade Underscore or replace it before production use.
- Does Backbone.js in this bundle require jQuery?
- Backbone 1.2 expects jQuery or Zepto for DOM manipulation and AJAX. This bundle packages Backbone and Underscore but does not include jQuery, so your host application must provide a compatible version. In a Laravel Vite setup, install jQuery through npm and expose it globally before loading Backbone.
- How do I publish the Backbone.js assets into my application?
- In Symfony, assets are typically exposed with assets:install or bundle asset configuration. Laravel has no equivalent vendor:publish hook for this Symfony bundle, so copy the files from vendor/rhapsody-project/backbone-js-bundle into resources/js/vendor and commit them. Copying the files gives you ownership so you can patch or replace Underscore independently of the Composer package.
- Is rhapsody-project/backbone-js-bundle actively maintained?
- Backbone upstream has been effectively dormant since version 1.4.0 in 2019, and this bundle pins the much older 1.2 line. The package version appears to track the bundled Backbone version, so a bump may change both PHP glue and JavaScript runtime. Assume there is no realistic upstream patch path and that remediation is your responsibility.
- What are alternatives to using Backbone.js in a Laravel application?
- Most modern Laravel applications use Livewire, Alpine.js, Inertia with Vue or React, or plain Vite modules instead of Backbone views. If you are maintaining an existing Backbone UI, bridge it gradually while building new features in the host stack. A full rewrite is usually not required just to remove this package.
- Can I safely use this bundle in production?
- Only with explicit risk acceptance. The bundled Backbone 1.2 and Underscore 1.6 pair is roughly a decade old and will produce unavoidable security audit findings. If you must proceed, vendor the files, upgrade Underscore to at least 1.12.1, pin a compatible jQuery version, and isolate Backbone to legacy screens with a documented migration plan.
Weaver
How can I help you explore Laravel packages today?