Closed joakimlemb closed 1 week ago
Investigation:
import-map-deployer's initial health check reads the import map, then writes it, then reads it again. Based on the BlobDownloadResponse
portion of the stacktrace, my guess is that it's failing during the read. This line might be the line calling into @azure/storage-blob
and triggering the error.
import-map-deployer upgraded some dependencies, but the dependency for @azure/storage-blob
was not upgraded (see git blame). Perhaps a dependency of azure/storage-blob was upgraded. I will try to replicate the issue.
I have replicated the issue locally and fixed it. It's related to Azure Storage's tslib dependency not working in Node 20. Upgrading to @azure/storage-blob@12.24.0
fixes it.
Unfortunately, the import-map-deployer tests don't work because the @azure/core-rest-pipeline
dependency doesn't function the same in Jest as in normal Node. See possibly-related https://github.com/Azure/azure-sdk-for-js/issues/28940
Released the fix for this in 5.0.0. The upgrade to Node 20 is a breaking change to import-map-deployer and shouldn't have been released as a patch.
Upgrading to 5.0 fixed our issue, thanks for the fast solution @joeldenning
After updating from 4.6.0 to 4.6.1 we are getting the following error:
Similear issues we found: https://github.com/Azure/azure-sdk-for-js/issues/25552 https://github.com/oven-sh/bun/issues/4067