Skip to content

Update dependencies (incl. fhir --> fhir-tool) #62

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
cmoesel merged 1 commit into from
Mar 8, 2026
Merged

Update dependencies (incl. fhir --> fhir-tool) #62

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 1 addition & 8 deletions DEPENDENCY-NOTES.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,14 +1,7 @@
As of 2025 March 28:
As of 2026 March 8:

The `npm outdated` command reports a dependency as outdated. It is not being updated at this time for the reason given below:

- `@types/node`: don't update until Node 22 is LTS version (currently Node 20).
- `chalk`: major version 5 is an esmodule and causes problems for jest. Keep updated to latest 4.x release.
- `commander`: major version 14 requires Node 20 and higher. Wait until community has had sufficient time to move off Node 18.

The `npm audit` command reports two vulnerabilities that we currently cannot resolve:

- `lodash`: bundled as a dependency in `fhir` and cannot be overridden. I've asked the maintainers to update the dependency.
See: https://github.com/lantanagroup/FHIR.js/issues/72
- `minimatch`: multiple dependencies use this (mainly dev dependencies) but have not updated yet. We cannot override because
the API has changed and is not compatible with the dependencies that use it.
Loading