Can't develop or deploy existing checkout extensions

I have a extenion only app and have several extensions in it that worked flawlessly before.

As of last week when I try to develop or deploy them I get the following errors:

09:31:52 │   line-item-compare-price │ ✘ [ERROR] Could not resolve "@remote-ui/core"
09:31:52 │   line-item-compare-price │
09:31:52 │   line-item-compare-price │
extensions/line-item-compare-price/node_modules/@shopify/ui-extensions/build/esm/utilities/registration.mjs:1:33:
09:31:52 │   line-item-compare-price │       1 │ import { createRemoteRoot } from '@remote-ui/core';
09:31:52 │   line-item-compare-price │         ╵                                  ~~~~~~~~~~~~~~~~~
09:31:52 │   line-item-compare-price │
09:31:52 │   line-item-compare-price │   You can mark the path "@remote-ui/core" as external to exclude it from the bundle, which will remove this
error and leave the unresolved path in the bundle.
09:31:52 │   line-item-compare-price │
09:31:52 │ address-length-validation │ Bundling JS function...
09:31:52 │ address-length-validation │ Running javy...
09:31:52 │ address-length-validation │ Done!
09:31:52 │               app-preview │ ❌ Error
09:31:52 │          delivery-options │ └  Build error. Please review your code and try again.
09:31:52 │ insurance-country-validat │ └  Build error. Please review your code and try again.
09:31:52 │          lease-code-input │ └  Build error. Please review your code and try again.
09:31:52 │   line-item-compare-price │ └  Build error. Please review your code and try again.

Anyone else run into the issue? What’s the solution?

Hey @Evonux - could you let me know which version of the CLI you’re using and try re-running the deploys using version 3.91.1? If the issue still pops up in the latest version, could you add the --verbose flag to the end of your deploy command and share that output here?

I can take a look on our end if it’s still failing for sure and investigate further.

Hi @Alan_G, I tried with 3.90, and then with 3.91.1 but the same issue persists.

The verbose output can be found on this pastebin, it’s too big to add here.

Thanks @Evonux - I’ll dig into this further for you and prioritize things on my end, appreciate you sharing the Pastebin logs!