bump to node 12 and update packages' #36
Open
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
updated nvmrc updated packages per npm's vulnerability fix option (with force)
Codecov Report
@@ Coverage Diff @@
## master #36 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 4 4
Lines 67 67
Branches 18 18
=========================================
Hits 67 67 Continue to review full report at Codecov.
|
|
As azure will deprecate azure-tools v2, and v3 requires node@12. I will have to fork this PR. |
|
Ridiculous that we are a year later and this hasn't been resolved |
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.
Azure Functions v3 supports Node 12 which is now LTS
This PR makes changes needed so it will install and run on Node 12.
I also bumped package versions just by running
npm audit fix --forceand deleted and recreated
package-lock.json.It seems to work fine.