medplum / medplum / 21651878090

92%

main: 92%

push

github

Add explicit type keyword + .d.ts extensions to fhirtypes imports for NodeNext compatibility (#8353)

* Add .js extensions to fhirtypes imports for ESM compatibility

The @medplum/fhirtypes package uses "type": "module" but the generated
type declarations use relative imports without file extensions. This
breaks TypeScript projects using moduleResolution: "nodenext" which
enforces strict Node.js ESM resolution rules.

This change adds .js extensions to all generated imports and re-exports:
- export * from './ResourceType.js'
- import { Resource } from './Resource.js'

The .js extension works correctly because TypeScript maps .js imports
to .d.ts files during type resolution.

Fixes #8348

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Signed-off-by: Ian Plunkett <1857868+ianplunkett@users.noreply.github.com>

* tweak(generator,fhirtypes): export type only, + .d.ts

Signed-off-by: Derrick Farris <derrick@medplum.com>

---------

Signed-off-by: Ian Plunkett <1857868+ianplunkett@users.noreply.github.com>
Signed-off-by: Derrick Farris <derrick@medplum.com>
Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
Co-authored-by: Derrick Farris <derrick@medplum.com>

16936 of 19201 branches covered (88.2%)

Branch coverage included in aggregate %.

4 of 4 new or added lines in 1 file covered. (100.0%)

30972 of 32704 relevant lines covered (94.7%)

13854.24 hits per line