This repository has been archived by the owner on Apr 17, 2023. It is now read-only.
Update @firebase/testing and release-it. #157
Closed
Conversation
This file contains 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
Run the following commands to resolve some probably unimportant vulnerabilities identified by 'npm audit': npm install --save-dev @firebase/[email protected] npm install --save-dev [email protected] It also provided a command for updating lodash, but when I ran it it pegged my laptop's CPU at 200% for more than half an hour before running out of memory and crashing.
|
@firebase/testing is deprecated and i'm switching away from it in #182 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Run the following commands to resolve some probably
unimportant vulnerabilities identified by 'npm audit':
npm install --save-dev @firebase/[email protected]
npm install --save-dev [email protected]
It also provided a command for updating lodash, but when I
ran it it pegged my laptop's CPU at 200% for more than half
an hour before running out of memory and crashing.