🚀 Feature Request: `wrangler pages dev --remote`

[F0rce]

Describe the solution

Hi everyone,

When developing frontend applications using Cloudflare pages, we use some of the CF- headers to validate some requests (for example, getting the cf-ipcountry to show the user a recommendation for switching languages).

There are a few more headers that are relevant to our logic, but at the moment we are unable to test these headers and the logic behind them without first deploying to pages, tailing the logs and then making some improvements to the code.

Maybe it's as simple as "copying" the logic from wrangler dev --remote to pages, but I haven't looked at it directly, nor do I know the exact logic behind wrangler.

Thanks in advance and appreciate all the work,
David

[buckett]

I had a similar issue where I was trying to debug some caching behaviour of fetch() in a pages function and allowing remote development would have simplified this.

[buckett]

Using the dashboard playground as outlined on: https://developers.cloudflare.com/workers/learning/playground/#using-the-playground allows quick iterating on code that runs on CF servers and may be helpful in some cases.

[baer]

For context, this is the file that runs wrangler pages dev. There is quite a lot of hard-coded local-only stuff in it like forcing the D1 database to local-${d1}. Unfortunately, I think this will be quite a lift.

[jadbox]

I'd like to bump up visibility as it's a blocker for multiple teams. We could not test our app against production via wrangler pages dev --remote as we had assumed. Without this, we cannot even test a page worker fix against production data.

[jerimiahwelch]

+1 for this feature. We often see different responses to local and CDN sub-requests. We don't have a simple way to preview or debug these differences.

[Markloev]

Also in need of a solution here, but specifically for me, I need a way to access remote Cloudflare KV/R2 after running 'wrangler pages dev'

[ctarmor]

I am suddenly facing issue. It's still broken.

wrangler pages dev ./build/client --remote

--remote it's not a valid parameter:

I've spent 4-5 hours trying to get this to work but no luck. I've gone thought all the remix / cloudfare docs and still can't access my remote D1 instance.

Wrangler CLI does work fine accessing remotely:

wrangler D1 execute job_listing_db --command "select * from listing"

trying accessing from remix always gets the error, table not found, becasue it's trying to run locally against a non-existent local D1.

Has anyone resolved this ??