Update code to support node-16 - #49
Conversation
|
Mmdixon (@Mmdixon) can we get your review on this and build binaries? Thanks! |
|
any updates on this? Mmdixon (@Mmdixon) |
|
Albert Coroleu (@acoroleu-tempus) Looks like the build failed because some of the dependencies are getting old and no longer hosted on the build servers (e.g. .NET core 2.1), I'll fix the build then get integration running again for this PR. |
|
Mmdixon (@Mmdixon) any progress here? |
|
Mmdixon (@Mmdixon) we'd like to upgrade our code to node16, this dependency is blocking us from doing so. Have you got time to review this PR? Thanks for your time |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Mmdixon (Mmdixon)
left a comment
Mmdixon (Mmdixon)
left a comment
There was a problem hiding this comment.
you should drop the package-lock.json changes.
|
the package-lock.json changes are needed since node 16 updated the schema for this file. which specific changes should I drop? Mmdixon (@Mmdixon) |
|
Mmdixon (@Mmdixon) any update on this? Thanks |
3 participants
No description provided.