You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With these 2, now yarn add applicationinsights emits:
error @azure/core-util@1.7.0: The engine "node" is incompatible with this module. Expected version ">=18.0.0". Got "14.21.3"
which means now it's a 2nd generation dependency having compatibility issues, and I have absolutely no idea which. Also, what if there are 10 more of these incompatibilities? I find it highly impractical, so I gave up. Any ideas?
Edit:
I didn't know you can have wildcard resolutions. This works:
The Azure SDK libraries for JavaScript will not be guaranteed to work on Node.js versions that have reached their end of life. Dropping support for such Node.js versions may be done without increasing the major version of the Azure SDK libraries.
Which seems wierd because if this was policy from the beginning, then the Node Compatibility section shouldn't even be included in the README because it could be invalidated at anytime even if this package hasn't bumped its version at all, such as now.
Trying
yarn add applicationinsights
onnode 14.21.3
, and gotSo I tried to resolve all incompatibilities by manually writing all dependency resolutions in
package.json
, and I'm stuck here:With these 2, now
yarn add applicationinsights
emits:which means now it's a 2nd generation dependency having compatibility issues, and I have absolutely no idea which. Also, what if there are 10 more of these incompatibilities? I find it highly impractical, so I gave up. Any ideas?
Edit:
I didn't know you can have wildcard resolutions. This works:
Still, I feel like this is more of a workaround, because if README claims ApplicationInsights supports
node 8
then it should work out of the box.The text was updated successfully, but these errors were encountered: