chore: allow to set orderbook urls using local storage

[alfetopito]

Summary

Use localStorage to set a custom backend endpoint

Supersedes #6003

To Test

1. Pick the url endpoints you'd like to use and set them with:
2. localStorage.setItem('orderBookUrls', JSON.stringify({ "1":"https://YOUR_HOST", "100":"https://YOUR_HOST" }))
3. Refresh the page
4. Check the network page

• Requests should be sent to the respective endpoints set above, for the chains specified

5. To clear it:
6. localStorage.removeItem('orderBookUrls')
7. Refresh the page

• Usual URLs should be used instead

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Updated (UTC)
cowfi	Ready	Preview	Nov 26, 2025 3:49pm
explorer-dev	Ready	Preview	Nov 26, 2025 3:49pm
sdk-tools	Ready	Preview	Nov 26, 2025 3:49pm
swap-dev	Ready	Preview	Nov 26, 2025 3:49pm
widget-configurator	Ready	Preview	Nov 26, 2025 3:49pm

1 Skipped Deployment

Project	Deployment	Preview	Updated (UTC)
cosmos	Ignored		Nov 26, 2025 3:49pm

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore/orderbook-api-url

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}