Jeremy Meng

@EmmaZhu suggested to add a browser version of `isNode` that just return false: https://github.com/Azure/azure-sdk-for-js/issues/21110#issuecomment-1537066462. One interesting thing for Electron is that it is also kinda of Client and there's some...

in Core v2 we do use a browser version of isNode from core-util. I will try porting it to core-http

still relevant

/azp run js - service-bus - tests

Will need to guard against the service issue for May release, as the service issue has not been fixed yet.

@ljharb thank you for the report! Quoting [our support policy](https://github.com/Azure/azure-sdk-for-js/blob/main/SUPPORT.md#microsoft-support-policy) here: > The Azure SDK libraries for JavaScript will not be guaranteed to work on Node.js versions that have reached...

Another reason we moved to NodeJS 18 quicker is that EOL of NodeJS 16 was aligning with EOL of OpenSSL 1.1.1. It's not wise to depend on an unsupported security...

should be resolved by PR #29414

currently blocked by `esm` not supporting null chaining operator, which is used in one of `glob`'s transitive dependencies.

dev-tool still depends on v9