Fix issues with outdated package-lock.json file. #1170
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Our
package-lock.jsonfile is outdated and our dependencies are a bit jumbled up.I didn't notice any issue when using
nodejs14but when usingnodejs16reveals several issues that I've tried to address in the PR:Update
typedocdependency to avoid impossible dep resolution (first reported Update typedoc from 0.21.2 to ^0.23.7. #1169)Regenerate
package-lock.json. Looks like it's "behind" package.json. I took this opportunity to uselockfileVersion: 2which is the default if you usenodejs16Using
firebase-adminv10.3.0 broke some unit test we had. Fixed in 2ee9549.