Weave Code
Nghttpbundle Laravel Package
pulpmedia/nghttpbundle
pulpmedia/nghttpbundle is a Symfony bundle for NG HTTP integration, providing configuration and service wiring that simplifies HTTP-related tasks in your application. It follows Symfony conventions, installs via Composer, and helps keep HTTP concerns organized and reusable across projects.
At a glance
Frequently asked questions about Nghttpbundle
- Can I install pulpmedia/nghttpbundle in a Laravel application?
- No. pulpmedia/nghttpbundle is a Symfony bundle that relies on Symfony's kernel and bundle-discovery system; Laravel has no equivalent mechanism, so composer require would at best install inert files and at worst fatal on Symfony-era class references. The Laravel-native equivalent is a CSRF meta tag plus Axios defaults in resources/js/bootstrap.js.
- What does pulpmedia/nghttpbundle actually do?
- Based on its structure, it is a Symfony bundle that wires configuration and services so AngularJS 1.x $http requests can carry Symfony's CSRF token and session context on same-origin calls. It includes a DependencyInjection extension and a public JavaScript asset. It is not a general-purpose HTTP client or router for Laravel.
- Is pulpmedia/nghttpbundle compatible with Laravel 10 or 11?
- No. It is a Symfony bundle, not a Laravel package, and it does not ship a Laravel service provider or Blade partial. Supporting Laravel 10 or 11 would require rewriting it as a service provider plus a view partial, which is not how the package is distributed.
- Which Symfony versions does this bundle support?
- The package follows Symfony 2.x-era conventions, including bundle inheritance and service definitions that break on Symfony 4 and later. There is no visible CI, test suite, or release history to confirm support for any modern Symfony version. Treat it as an abandoned artifact rather than a maintained compatibility target.
- Does pulpmedia/nghttpbundle work with Angular 2+ or modern Angular?
- No. It targets AngularJS 1.x and its $http and $httpProvider interceptor APIs, and AngularJS reached end-of-life in December 2021. Modern Angular uses HttpClient and HttpInterceptor, which share no API surface with this bundle's client-side code.
- How do I add CSRF tokens to AngularJS requests in Laravel without this bundle?
- Render a csrf-token meta tag with csrf_token() in your Blade layout, then set window.axios.defaults.headers.common['X-CSRF-TOKEN'] in resources/js/bootstrap.js for Axios requests. For AngularJS, configure $httpProvider.defaults.headers.common to read the same meta tag. That reproduces the bundle's intent with zero third-party surface in under a day, including tests.
- Is pulpmedia/nghttpbundle maintained or safe for production?
- It shows zero stars, zero dependents, and no visible CI, tests, or release history, which points to an abandoned 2015-era artifact with a bus factor of one. The security surface is small—a JavaScript asset and a DI config—so CVE exposure is unlikely, but unmaintained means you become the maintainer from the moment you fork it. The MIT license makes forking legally clean, but production adoption still entrenches two end-of-life technologies.
- What are alternatives to pulpmedia/nghttpbundle for Laravel?
- Use Laravel's native CSRF handling: a csrf-token meta tag rendered with csrf_token() and Axios defaults in resources/js/bootstrap.js using the X-CSRF-TOKEN header. For a modern Angular frontend, implement an HttpInterceptor that reads the same meta tag. No third-party package is needed.
- How do I migrate from pulpmedia/nghttpbundle to a Laravel-native approach?
- Do not install the package. For greenfield Laravel plus modern Angular, implement the meta tag, Axios defaults, and HttpInterceptor pattern directly. For legacy Symfony 2.x plus AngularJS 1.x, extract the bundle's JavaScript asset and configuration semantics into your own asset pipeline, replace the DI wiring with a controller or Twig extension that emits the bootstrap config, then remove the bundle from composer.json. This is a lift-and-shift of behavior, not a fork of the codebase.
- Does pulpmedia/nghttpbundle have tests or documentation?
- There is no visible CI, test suite, or release history in the repository, and the README excerpt is absent. Treat the package as a pattern reference rather than a dependency. If you fork it, add tests for CSRF header injection and config emission before relying on it.
Weaver
How can I help you explore Laravel packages today?