- Can I use pandawan-technology/neo4j-bundle in a Laravel application?
- No, not idiomatically. This package is a Symfony bundle that relies on Symfony's Dependency Injection container, bundle registration, and YAML configuration; it has no Laravel service provider, facade, or config publish command. In Laravel you would either fight the Symfony bootstrapping assumptions or bypass the bundle and use the underlying graphaware/neo4j-php-client directly, at which point the bundle adds nothing. Use the official Neo4j PHP driver inside a thin Laravel service provider instead.
- Is pandawan-technology/neo4j-bundle still maintained?
- No. The repository description explicitly states it is NOT MAINTAINED ANYMORE and redirects to neo4j-contrib/neo4j-symfony. It has 1 star and 0 dependents, so there is no downstream community to validate compatibility or inherit maintenance. Treat it as a reference implementation and scoping artifact, not a dependency for new work.
- How do I install the Neo4j bundle with Composer?
- In a Symfony project you would historically run composer require pandawan-technology/neo4j-bundle, register the bundle in the kernel, and configure connections in YAML. In a Laravel project you should not add it to composer.json because the package is deprecated and unverified against current PHP and framework versions. If you are auditing it for legacy context, expect stale Composer constraints that may resolve to an ancient locked dependency set.
- How do I configure Neo4j connection settings?
- The bundle expects YAML-based connection settings that are injected through Symfony's Dependency Injection container, and it supports multiple named connections. That configuration model does not map to Laravel's config directory or environment handling without custom glue. For Laravel, create a config/neo4j.php file and bind a connection factory in a service provider instead.
- Does this bundle support multiple Neo4j connections?
- Yes, the bundle advertises support for multiple named connections defined in YAML and exposed through Symfony's service container. However, that feature is tied to Symfony configuration conventions rather than Laravel's config repository. If you need multiple graph connections in Laravel, wrap the official driver in a small connection manager you own.
- Which Neo4j server versions does this bundle support?
- This is unverifiable from the available information, and the embedded driver's Bolt protocol support is likely to lag modern Neo4j releases. Cypher and Bolt changes in Neo4j 5.x are unlikely to be reflected in an unmaintained wrapper, so silent behavioral drift is plausible. Confirm your target Neo4j server version and use the official neo4j/neo4j-php-client, which tracks server releases.
- Does this bundle work with Laravel Octane and queue workers?
- No, not cleanly. The Symfony container and bundle lifecycle assumptions conflict with Laravel's long-lived worker model under Octane and queue consumers, where connection state must be reset or health-checked between jobs. A thin Laravel service provider around the official driver gives you explicit control over connection handling and lifecycle.
- What is a maintained alternative to this Neo4j bundle?
- For Symfony, the maintainer redirects to neo4j-contrib/neo4j-symfony, which you should validate for release cadence before committing. For Laravel, the correct evaluation set is driver-level packages: the official neo4j/neo4j-php-client, or laudis/neo4j-php-ogm if you genuinely need entity mapping. Wrap the chosen driver in a single service provider plus config file and keep the wrapper thin.
- How should I test a Neo4j integration in a Laravel app?
- Mock or fake the connection factory and client interface for unit tests so tests do not require a live graph database. Add a small integration suite against a containerized Neo4j instance to verify Cypher queries and Bolt compatibility for your target server version. Avoid depending on Symfony bundle service wiring in tests, since that layer would not exist in a Laravel-native setup.
- Is pandawan-technology/neo4j-bundle safe for production use?
- It carries high risk on every axis. Abandonment is already realized, there is no security disclosure channel or patch path for transitive dependency CVEs, and PHP or framework version drift has no remediation short of forking. If you proceed anyway, you must assign an owner for the fork on day one and verify the Neo4j server version in scope.