Commit updated package-lock.json
to fix ts build
#722
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Typescript builds have been down for around a month.
Looking at the most recent
main
build action run, it is due to packages missing from thepackage-lock.json
:This is likely due to PRs being merged without
npm install
being run in the root which results inpackage.json
being out of sync with the lock file.This PR just runs
npm install
to update the lock with the missing packages.Motivation and Context
This is blocking recent updates to the servers being release on NPM and means updates are not getting pulled when people try to install these servers via
npx
.How Has This Been Tested?
All GitHub actions are now passing.
Types of changes
Checklist