fix(web): bundle p-retry into dist/web browser build

[edenbuilds]

Summary

• Web Rollup target now uses @rollup/plugin-node-resolve and no longer marks p-retry as external, so dist/web/index.mjs has no bare "p-retry" specifier.
• Node/CJS builds unchanged (still externalize p-retry).

Test plan

• Published dist/web/index.mjs contains from 'p-retry'; bundling with p-retry inlined removes that bare import.
• Rollup web config: external excludes p-retry; plugins include node-resolve.

Fixes #1330

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[edenbuilds]

I have read the CLA Document and I hereby sign the CLA

[Varun-S10]

Hi @edenbuilds, Thank you for your patience. It looks like this branch is currently out-of-date with the base branch. Could you please update the branch to bring it up to date? This will allow us to complete our verification.

[edenbuilds]

Updated the branch to current main in 3d2ab2e8 without rewriting history. The refresh exposed that current p-retry@4 is CommonJS, so I added @rollup/plugin-commonjs to the web-only plugin chain alongside node-resolve. The full package build now passes; dist/web/index.mjs contains no bare p-retry import, imports successfully as a standalone module (165 exports), and git diff --check passes.

[edenbuilds]

CLA follow-up: the signed agreement is now recognized and cla/google passes. The prior failure came from one stale merge commit attributed to a different GitHub identity/email; I collapsed the already-verified tree onto current main as the single edenbuilds commit aee1cf54. The code diff is unchanged; the full build passes and the standalone web artifact still imports with no bare p-retry specifier.

[Varun-S10]

Hi @edenbuilds, Thank you for your contribution. We have checked the code changes. I will escalate this to the team, and the PR will be reviewed. Thank you for your patience and understanding.

[edenbuilds]

Thanks @Varun-S10. I have refreshed the branch through current main (7fe15a61, including the 2.20.0 release) and re-verified it locally:

• npm run lint
• npm run unit-test — 695 specs, 0 failures
• npm run build
• confirmed dist/web/index.mjs has no external p-retry import and loads successfully with 165 exports

The verified update is pushed at 911c427c and is ready for maintainer review.

[edenbuilds]

Refreshed the branch onto current upstream main in non-rewriting merge commit bf30075. The PR diff remains limited to bundling p-retry for the web build; GitHub now reports the branch as mergeable, with maintainer review/check completion still outstanding.

[edenbuilds]

Follow-up on the remaining CLA gate: the current cla/google output accepts edenbuilds, but rejects merge commit bf3007507706051f969f6595daf7f1ae500f77e2 because GitHub attributes its author to omkar1work. That September 21 base-refresh commit reintroduced the identity mismatch; the current failure is not a code or build failure.

Could the team advise whether the existing CLA can cover that historical author identity, or whether you need a branch-history correction? I have left the published history intact.

[edenbuilds]

Squashed the branch into a single commit authored as edenbuilds, so cla/google now passes. The code is unchanged (same tree as the previous head).