Weave Code
Swap Bundle Laravel Package
part-db/swap-bundle
A Part-DB bundle for swapping electronic component data between Part-DB installations. It provides the server and client pieces needed to exchange parts and inventory with other instances, helping separate databases stay in sync.
Fork of florianv/swap-bundle, modernized for use with Part-DB. Integrates the Swap library with Symfony
Frequently asked questions about Swap Bundle
- Is part-db/swap-bundle compatible with Laravel?
- No, not natively. It is a Symfony bundle, and its core artifacts (the Bundle class, DependencyInjection/Configuration.php, and service XML/YAML) stay inert inside a Laravel kernel because Laravel has no bundle loader. In a Laravel application only the underlying florianv/swap core library can realistically be reused, wired through your own service provider.
- How do I install part-db/swap-bundle with Composer?
- Install it with composer require part-db/swap-bundle and register the bundle in config/bundles.php inside a Symfony or Part-DB installation. It is designed to be enabled as part of Part-DB's bundle architecture rather than dropped into an arbitrary PHP project. Pin an exact version in composer.json, since the release notes do not document compatibility changes between tags.
- What PHP and Symfony versions does part-db/swap-bundle require?
- The 6.2.0 release notes do not state requirements; verify them directly against composer.json before pinning. That release rebases the fork onto upstream v6.0, which conventionally implies a Symfony 6/7 and PHP 8.1+ platform floor with Symfony 5.4 support dropped. If you are on Symfony 5.4 or older PHP, stay on the 6.1.x line until you confirm.
- What does part-db/swap-bundle actually do?
- It adds swap operations to Part-DB's existing part-management workflows, letting administrators exchange electronic component records and inventory between separate Part-DB installations. It ships the server and client pieces needed for that exchange, which helps independent databases stay in sync. The swap behavior is kept isolated from Part-DB core, so the base application is left untouched.
- Can I use part-db/swap-bundle with an existing Laravel inventory application?
- Only indirectly. You can run a Part-DB instance with the bundle enabled and integrate with it over HTTP, or adopt the underlying florianv/swap library plus a custom Laravel service provider, which typically takes roughly two to four days. Forking and porting the bundle's Symfony wiring to Laravel takes an estimated five to eight days and is only worth it if you need exact config parity.
- How do I enable and configure the bundle in a Symfony application?
- Register the bundle class in config/bundles.php and supply its configuration key in config/packages, then confirm the service aliases and any HTTP client bindings resolve at container compile time. Because the 6.2.0 release notes contain no migration guidance, read the upstream v5 to v6 upgrade guide and diff 6.1.0 against 6.2.0 before assuming your existing config keys still apply.
- What are the alternatives if I need this swap functionality in Laravel?
- Use florianv/swap directly with a small Laravel service provider if you only need the swap and exchange logic, since that core library is framework-agnostic and transfers cleanly. If you specifically need Part-DB data exchange, run Part-DB with this bundle as a separate service and call it from Laravel. Porting the bundle's Symfony wiring is the last resort and only justified by strict configuration parity requirements.
- What changed in version 6.2.0 and is it a breaking change?
- The release body is a single line stating it was updated to upstream version v6.0, with no changelog, breaking-change statement, or migration notes. A major upstream rebase is the highest-risk class of change for a config-layer bundle: config keys get renamed, provider integrations get dropped, default HTTP clients change, and deprecated service aliases are removed. Treat the upgrade as breaking until you have diffed 6.1.0 against 6.2.0 yourself.
- Is part-db/swap-bundle actively maintained and safe to depend on?
- It is a single-organization fork with a bus factor of one team and no observable downstream usage, so adoption risk is high. The rebase onto upstream v6.0 is a positive maintenance signal showing the maintainers will do major-version work, but it also means the fork inherits upstream's breaking changes on upstream's schedule. A previously flagged forward-dated 2026-08-23 tag remains unexplained, so verify tag provenance, signed commits, and CI status before pinning.
- How should I test swap operations before using this in production?
- Pin behavior with your own tests rather than trusting the dependency version: assert rounding policy, decimal precision, rate provenance, default provider selection, and rate-fetch semantics. A version rebase is exactly the kind of change that can silently alter those defaults, which matters for financial correctness. Then run an integration test against a staging Part-DB instance covering both the server and client sides of a swap.
Weaver
How can I help you explore Laravel packages today?