There is no non-local `wrangler pages dev` at the moment.
There is no non-local
wrangler pages dev
GWe’re still thinking about it. What would you expect
npx wrangler pages dev --remote
Kjust to be clear, it's local only atm, right?
GYes.
Gwrangler pages devwrangler pages devWrangler let’s you test Workers locally or remotely. We don’t have a remote equivalent for Pages yet.
I was just wondering what you thought a remote version might look like. No biggie if you don’t have any thoughts on that. I was just curious
KThat's what preview builds are for
KCloudflare has a big network and each deploy goes to all of them
KJust rendering changed content is a goal, but I don't think we are anywhere near getting it
GHere’s the original announcement: http://blog.cloudflare.com/announcing-wrangler-dev-the-edge-on-localhost/
The Cloudflare Blog
A few weeks ago we announced a release candidate for wrangler dev — today, we're excited to take wrangler dev, the world’s first edge-based development environment, to GA with the release of wrangler 1.11.
GYou can also use
cloudflared tunnel
Jseems like it was delayed
Jnow it shows 153
GYup
Kyes atm
Ki don't think so, the runtime isn't node
KCloudflare Workers requires us to bundle our entire worker code into a single file.
For bundlers to be able to discover & bundle the entire dependency tree, we need to use dist/server/importBuild.js.
Kare you doing that?
Kcan you pastebin it?
Kalso have you read the blog post?
Kthat might be helpful
GWe're aware of a bug on Windows, which I'm hoping to fix early next week: https://github.com/cloudflare/wrangler2/issues/32
GitHub
under windows wrangler2 fails due to an incorrect path given in the automatically generated routes.mjs config file from pages-functions-compiler. to recreate this issue: cli: npx wrangler pages dev...
GFeel free to follow that issue to be notified when the fix is live.
GSorry for the inconvenience in the meantime.
GYou can use the wrangler 2.0 beta to test Pages functions locally.
GYou need to use
--binding for now, but be aware that secrets aren't available in production just yet.GSecrets are pretty close to complete. Just a couple more things needed to get that over the line. In the meantime, you could use a KV namespace if that's not too much hassle.
EThat is certainly interesting. Do you send a request to a
http or https URL?