-
Notifications
You must be signed in to change notification settings - Fork 141
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
Dependency incompatible with node < 18 #1274
Comments
It's good to know, except for having to inject that into every node project. |
@azure/core-auth claims that this is policy:
Which seems wierd because if this was policy from the beginning, then the |
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: