- Is mspa/neo4j-bundle a Laravel package?
- No. mspa/neo4j-bundle is a Symfony bundle, not a Laravel package. It has no Laravel service provider, facade, or config/neo4j.php publish path. Laravel cannot register Symfony bundles, so using it requires porting the wiring.
- Can I install mspa/neo4j-bundle in Laravel with Composer?
- Composer may install the dependency if constraints resolve, but that does not give you a working Laravel integration. The bundle expects registration in config/bundles.php and compilation by Symfony's Kernel. Laravel has a different container, config repository, and bootstrapping lifecycle. You would need to reimplement the service wiring in a Laravel provider.
- Which Laravel versions does mspa/neo4j-bundle support?
- There is no official Laravel version support because this is a Symfony bundle. Its composer.json is likely pinned to Symfony 4 or 5 era components, which can conflict with Laravel 10 or 11's Symfony component pins. Check the actual constraints before assuming compatibility.
- What Neo4j PHP driver does mspa/neo4j-bundle use?
- The evaluation notes it typically wraps graphaware/neo4j-php-client for Bolt or HTTP access, but the bundle does not clearly document the exact dependency. Inspect composer.json to confirm the client and version. The maintained successor to consider is laudis/neo4j-php-client.
- Does mspa/neo4j-bundle support Bolt or only HTTP?
- The context does not confirm whether mspa/neo4j-bundle supports Bolt or only HTTP. That behavior depends on the underlying Neo4j client it wraps. Bolt is binary and pooled, which matters for latency and throughput. Verify the driver transport before committing.
- Is mspa/neo4j-bundle safe for production Laravel apps?
- Treat it as high risk for production Laravel use. It has 0 stars, 0 dependents, a single author, no evident tagged releases, no CI signal, and no test suite. There is also no security disclosure process. Adopting the underlying driver and owning the integration layer is safer.
- How do I integrate Neo4j into Laravel without this bundle?
- Depend on laudis/neo4j-php-client or the original graphaware driver directly. Create a Laravel service provider, config/neo4j.php file with host, port, scheme, auth, database, pool size, and timeout, plus a Neo4jManager singleton and facade. Abstract access behind a GraphRepository interface so you can test with an in-memory fake. Bind app()->terminating() to close the driver and clean up sessions for queue workers and Octane.
- What are alternatives to mspa/neo4j-bundle for Laravel?
- Use laudis/neo4j-php-client, the maintained successor to graphaware/neo4j-php-client, and build a small Laravel package around it. The bundle itself adds little beyond thin container glue. A Laravel-native integration needs a service provider, config file, facade, and manager singleton. There is no validated Laravel-native Neo4j package identified in this evaluation.
- How should I test a Laravel Neo4j integration ported from this bundle?
- Define a GraphRepository port in your domain layer and use an in-memory fake for unit tests. Add integration tests against a real Neo4j instance or testcontainer to verify Bolt connectivity and Cypher behavior. Test session cleanup and driver shutdown for long-running workers. Do not rely on the bundle for test coverage because none is evidenced.
- Does mspa/neo4j-bundle support Neo4j 4.x or 5.x and transactions?
- The evaluation flags Neo4j 4.x versus 5.x support and Bolt protocol compatibility as unknown. Transaction and session semantics are also unclear, including whether it opens implicit sessions per call or exposes a managed lifecycle. For queue workers and Octane you need explicit cleanup and a well-defined lifecycle. Confirm these details against the underlying driver before any commitment.