carpusherw
carpusherw
This seems to be fixed in v3.0.0
@fafiorim It's not a good practice to update resources outside of the stack. I would suggest the alternative solution to update the document. Does that work for you?
Also filed https://github.com/AzureAD/microsoft-authentication-library-for-js/issues/5302 to see if adal-node still supports security update.
Even if the adal-node gets updated this time > adal-node is deprecated and will no longer be receiving any updates as of December 31st, 2022 https://github.com/AzureAD/microsoft-authentication-library-for-js/issues/5302#issuecomment-1279245106
I also bumped into the cycle error although with different resources. It happens to be that I didn't update all the output references. You could double check if that's also...