Closed FrederikFrederiksenMancofi closed 1 year ago
Perhaps this could be fixed by locking @azure/core-rest-pipeline and its dependence on @azure/core-util, but I guess such a fix would only be temporary unless backwards compatibility is a high priority of this project.
It would be nice though if package version references in package lock were a bit more ~ and a little less ^
I hit this issue as well on Node 10.
Same issue. According to azure console the version is v14.20.0 (node -ver) WEBSITE_NODE_DEFAULT_VERSION = 14.15.0
Locking @azure/core-util
to 1.2.0
using npm overrides is a workaround for us.
Locking down the dependency version for now, we will look into removing this dependency entirely if possible, will be releasing a new version of this package later today.
With the release of a new @azure/core-rest-pipeline v1.10.3 and its dependence on @azure/core-util v.1.3.0 I'm experiencing issues in my NodeJS v8.9.0 environment. The new version of core-util utilizes globalThis, which came with the release of node 12, and it results in the following error: