-
-
Notifications
You must be signed in to change notification settings - Fork 362
feat(retry-plugin): add getRetryPath in retry plugin to support users to customize retry path #4023
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
… to customize retry path
🦋 Changeset detectedLatest commit: adc6f1d The changes in this PR will be included in the next version bump. This PR includes changesets to release 36 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
✅ Deploy Preview for module-federation-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
…hecking in scriptCommonRetry
…try and add unit tests
Can you provide more info for This is very useful to choose suitable url if users have multiple backup urls |
feat(retry-plugin): add getRetryPath in retry plugin to support uses to customize retry path.
Description
Allow rewriting request URLs during retries to switch fallback domains, bust caches, or route traffic.
New Options:
fetch.getRetryPath?: (url: string) => string
script.getRetryPath?: (url: string) => string
Behavior:
Before each retry, the plugin calls getRetryPath(originalUrl) to compute the retry URL. If not provided, the original URL is used.
Example
Notes
Related Issue
Types of changes
Checklist