New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Need support for Node.js 20 #4550
Comments
@ramfattah Any news to support the current nodejs LTS |
Also waiting for Node.js 20 Support... |
+1 We were hoping to update our project to node 20 but were limited to node 18 due to this dependency. |
Any news on this one @microsoftopensource / or maybe @ceciliaavila? |
So until the dependency is being updated you could just overwrite the dependency globally in [...] "overrides": {
"@azure/msal-node": "2.6.0"
},
"dependencies": {
"@azure/msal-node": "2.6.0", [...] |
Are there plans to upgrade to @azure/msal-node v2 and as a result support Node 20? |
@alexnault Yes. But there is a complication. While it's out of support, we still have a healthy number of customers on Node 16. Not good manners to just drop it without a heads up. For the next few releases, the release notes will include a notice about updating to Node 18+. Does elovins suggestion work for you? |
@tracyboehrer Great to hear that Node 20 support is on the horizon! I understand that dropping support for Node 16 is a breaking change. To me, this should warrant a major version upgrade (botbuilder@5.0.0) over a notice, like @azure/msal-node did. Meanwhile, we added "overrides": {
"@azure/msal-node": "^2.6.1"
} Cheers! |
is error @azure/msal-node@1.18.4 really not support node 20?
|
Hey, what's the status of this? Waiting for this to be implemented for OfficeDev/TeamsFx#10849 |
Could you please give us an update on this matter? |
Node.js 20 will be designated as the active LTS version as of October 24, 2023.
The SDK has a dependency on
@azure/msal-node
, which appears to be outdated. Running thenpm install
commandresults in warnings due to its incompatibility with Node.js 20.The text was updated successfully, but these errors were encountered: