Weave Code
Edifact Bundle Laravel Package
progrupa/edifact-bundle
A Symfony bundle that brings EDIFACT EDI handling to your application, wrapping the progrupa/edifact library so you can parse, read and generate electronic business documents through Symfony services and configuration.
At a glance
Frequently asked questions about Edifact Bundle
- Can I use progrupa/edifact-bundle in a Laravel application?
- Not directly. It is a Symfony bundle that relies on Symfony's Bundle class, Extension/Configuration tree and kernel bootstrapping, and Laravel has no auto-discovery mechanism for Symfony bundles, so it would sit inert in a Laravel app with no service provider registered and no config merged. The practical path is to require the underlying progrupa/edifact library and expose it through your own Laravel service provider and facade.
- How do I install progrupa/edifact-bundle?
- In a Symfony project you would run composer require progrupa/edifact-bundle and register the bundle in config/bundles.php. Check the Packagist metadata first, because the package has no community traction and the metadata may be stale. In Laravel, skip the bundle entirely and require progrupa/edifact instead.
- Does progrupa/edifact-bundle support Laravel 10, 11 or 12?
- There is no declared Laravel support because the package is a Symfony bundle, not a Laravel package. Its PHP version constraint follows the upstream parser and the Symfony releases it was built against, which can pin you to an older framework era. Verify the composer.json constraints before assuming compatibility with current Laravel versions.
- How do I parse an EDIFACT interchange with progrupa/edifact?
- The upstream library parses UNB/UNZ envelopes and UNH/UNT message segments, and traverses segments, elements and composites. Wrap it behind an internal contract such as an EdifactParser interface with a parse method returning an Interchange, implemented by a thin adapter. That keeps the third-party types out of your domain code and lets you swap parsers later.
- Does this package generate outbound EDIFACT documents?
- The bundle is a thin wrapper and the upstream parser is primarily oriented toward reading interchanges, so outbound generation coverage is unclear. Producing correct outbound documents means getting segment ordering, mandatory and conditional rules, and partner-specific deviations right, which is materially harder than parsing. Treat outbound as separate scope you will likely build yourself.
- Does progrupa/edifact-bundle validate messages against ORDERS D96A or INVOIC D01B?
- No. It addresses the syntax layer only, covering envelopes and segment traversal, and does not enforce message-type schemas, MIG mandatory and conditional rules, or code-list validation. Assuming a partner hands you syntactically valid files, you would still need to build validators and the mapping layer to your domain objects. Budget for that work explicitly.
- Is progrupa/edifact-bundle actively maintained?
- The signals are poor: zero stars, zero dependents, no issue triage, no security advisories, and a bus factor of one. There will be no CVE response if a parser bug is found, so you carry the risk. If you adopt it, fork it, pin versions, and pin the behaviours you rely on with your own tests.
- How should I test EDIFACT parsing in a Laravel app?
- Use golden-file tests: store representative partner files as fixtures and assert the parsed interchange structure against each one. Cover the sharp edges explicitly, including the optional UNA service string advice that redefines delimiters, the release/escape character, charset switching (UNOA/UNOB/UNOC), multi-message interchanges, and trailing-segment tolerance. With no CI or coverage signal from the package, every behaviour you depend on must be pinned by your own tests.
- What are the alternatives to progrupa/edifact-bundle for PHP?
- Options include requiring the progrupa/edifact library directly, adopting a more actively maintained PHP EDIFACT parser, or outsourcing translation to a commercial EDI gateway or EDI-as-a-service. Compare the 24-month cost of self-maintaining an unmaintained parser against the vendor fee, including the mapping and validation work that neither option removes. Run a short spike with real partner files before committing.
- How do I wire progrupa/edifact into Laravel's service container?
- Require progrupa/edifact with Composer, or vendor it if the Packagist metadata is stale. Define an EdifactParser interface in your application, implement a ProgrupaAdapter that delegates to the library, and bind the interface to the adapter in a dedicated service provider. Optionally add a facade for ergonomic access, and keep all third-party types out of your controllers and domain services.
Weaver
How can I help you explore Laravel packages today?