primer/components fails with cryptic error

[shawnbot]

You can see in this run and this log that the action is failing with:

deploy error: Error: Unable to get deployment URL from now:

I noticed in the log of the previous successful run that it was running @primer/[email protected], so I pinned it with primer/[email protected] and that worked.

So the question is, what changed between 2.0.0 and 2.2.0 that would cause this? /cc @emplums

[shawnbot]

A couple of ideas:

• It might be because now isn't a dependency in Components, but that wouldn't explain why it was working before.
• Maybe a new release of now broke this action? It's possible that they broke printing the URL to stdout, which we rely on to get the "root" deployment URL.

The fact that there's no output from npx before the error might clue. I'd like to test this in another repo that doesn't have it installed in package.json.

[shawnbot]

Just bumping this with a thought: if we're able to parse out certain types of errors from now's stderr output, we could probably just retry deployment (say, 3 times?) if it fails with a known "flaky" error like the one here:

> Error! Uploading failed. Please try again.

At least, my assumption is that when the error says "Please try again", it's probably because Zeit folks know that the error can be worked around by retrying? 😬