fix: add padding to hero CTA buttons on mobile#361
Conversation
- Add Dune, PostalForm, Prospect Butcher, Stripe Climate - Update AgentMail (new URLs, realm, endpoints, brand icon) - Update Alchemy (mpp.alchemy.com, session intent) - Update Browserbase (x402.browserbase.com) - Remove X/Twitter endpoints from StableSocial - Add STRIPE_PAYMENT defaults for Stripe-based services - Move Alchemy below Parallel in listing order
VERCEL_BRANCH_URL was used as the baseUrl for preview deployments, which
Vocs injects as a <base href> tag. When visiting via the deployment-specific
URL (e.g. mpp-{hash}-tempoxyz.vercel.app), all relative fetches resolved
against the branch URL instead — causing CORS failures on /api/services
and RSC requests.
This was previously masked by Vercel Deployment Protection (password auth)
which canonicalized traffic to the branch URL. After removing password auth,
the mismatch is exposed.
Fix: prefer VERCEL_URL (matches the visited URL) over VERCEL_BRANCH_URL.
Services: Mapbox, RentCast, Grok, Stability AI, Hunter, Replicate, BuiltWith, Suno, OpenWeather, Perplexity, Diffbot, Mathpix, Judge0, Browser Use, Clado, EDGAR, EDGAR Search, Laso Finance
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 87106246e4
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| payment: TEMPO_PAYMENT, | ||
| endpoints: [ | ||
| { | ||
| route: "POST /api/browser-use-mpp/run-task", |
There was a problem hiding this comment.
Make Browser Use routes relative to the serviceUrl
Because serviceUrl already includes /api/browser-use-mpp, this endpoint path makes every copied/example URL come out as .../api/browser-use-mpp/api/browser-use-mpp/.... Both ExpandedDetail (src/components/ServicesPage.tsx:3469) and handleCopyEndpoint (src/components/ServiceDiscovery.tsx:911) prepend baseUrl to ep.path, so users browsing /services or copying from the discovery view will hit a nonexistent route for every Browser Use endpoint.
Useful? React with 👍 / 👎.
| payment: TEMPO_PAYMENT, | ||
| endpoints: [ | ||
| { | ||
| route: "POST /api/laso-mpp/auth", |
There was a problem hiding this comment.
Make Laso routes relative to the serviceUrl
The Laso entry has the same double-prefix problem: serviceUrl already ends with /api/laso-mpp, but the endpoint paths repeat that segment. In the current UI, ExpandedDetail and handleCopyEndpoint build URLs as ${baseUrl}${ep.path}, so copying or opening any Laso endpoint from the services/discovery pages produces .../api/laso-mpp/api/laso-mpp/... instead of a callable URL.
Useful? React with 👍 / 👎.
Adds responsive horizontal padding to the hero CTA buttons so they don't sit edge-to-edge on mobile screens.
px-4 sm:px-0for side breathing room on mobilepx-3 sm:px-5(smaller on mobile, original on desktop)gap-3 sm:gap-4(slightly tighter on mobile)