If your project compiles with --module NodeNext (or node16) and leaves
skipLibCheck off — the TypeScript default — @getpeppr/sdk 5.4.0 failed
your build before it ran a line of your code. One published declaration —
dist/core/status-precedence.d.ts — imported a type without its .js
extension, and under those module settings TypeScript rejects extensionless
relative imports with TS2835. A two-line consumer was enough to reproduce:
import { Peppol } from '@getpeppr/sdk';
void Peppol;
5.4.1 ships the corrected declaration. No API, type or behavioural change —
the only runtime-visible difference is the SDK version string sent in the
User-Agent header. Projects using moduleResolution: bundler, or compiling
with skipLibCheck: true, never hit the build failure at all.
npm install @getpeppr/sdk@5.4.1
The package now tests for this: the release candidate is packed, installed
into a fresh strict NodeNext project, and compiled without skipLibCheck as
part of the package's own test suite (npm test). Publishing a prebuilt
tarball would bypass that check — which is why the release procedure always
publishes from packages/sdk/, where the suite runs first.