Generated page. Written from IdaMilk/SunApps_EDI at commit 3a58c65 on 2026-07-28, version 0.0.1. No README; short by design.
SunApps EDI
What is it?
An early EDI service, described in its package.json as "846/940/945 electronic data interchange processing" — three transaction sets, handled by a small Express app with a partner resolver and a state map.
Status
Superseded by Suntado EDI. Last activity April 2026, still at version 0.0.1.
The successor is unambiguous. Suntado EDI handles nine transaction sets rather than three, has a partner and transaction registry rather than a single resolver, persists transmissions and control numbers to SQL Server, supports SFTP, AS2 and API transports, and is actively developed.
The naming is genuinely confusing and worth pinning down:
| This repository | The live one | |
|---|---|---|
| Repository | SunApps_EDI | Suntado_EDI |
| Package name | sunapps_edi | sunapps_edi |
| Version | 0.0.1 | 1.4.2 |
| Status | Superseded | Active |
Both packages are named sunapps_edi. The repository name is the only reliable way to tell them apart — check which one you have open before making a change.
What it contained
| Path | Role |
|---|---|
services/edi/ediService.js | Document processing |
services/edi/partnerResolver.js | Partner lookup |
services/edi/stateMap.js | State mapping |
services/emailTemplates.js | Notification templates |
clients/coreClient.js | Calls back to the Core API |
No database and no X12 library — a thin service that leaned on the Core API rather than owning EDI itself. That limitation is essentially why the successor exists.
Repository
| Repository | IdaMilk/SunApps_EDI |
| Version | 0.0.1 |
| Primary language | JavaScript (Node, CommonJS) |
| Files | 15 |
| Last activity | 2026-04-15 |
| Status | Superseded |
| README | None |
It retains full deployment workflows, so it could still be deployed by accident. Archiving it would remove that possibility and resolve the name collision at the same time.