-
Notifications
You must be signed in to change notification settings - Fork 335
Run wrangler dev locally #1820
Comments
I agree fully! There should be a way to develop and run tests locally without the requests being routed to the Cloudfare edge.. Other cloud providers such as Azure have support for local development environments. There should be an official support maintained by Cloudflare @rita3ko :) In the mean time you can look into jdanyow's packages collection: Oh yea, and there are so many issues with wrangler login, timeouts, bad gateways and panick, that would be mitigated with local development environment: Thanks! |
I've since published https://github.com/RaeesBhatti/cloudflare-kv-isomorphic which emulates Cloudflare KV API's when running locally on NodeJS. This allows me to develop the site without |
This issue has been automatically marked as stale because it has not had recent activity in the last 180 days. It will be closed if no further activity occurs in the next week. Please feel free to comment if you'd like it to remain open, and thank you for your contributions. |
I guess this is no longer relevant with the new miniflare release |
💡 Feature request
Describe the feature
It seems like my requests to
wrangler dev
are being routed to Cloudflare servers. This is causing unnecessary latency in when I make the changes and when they're realized in the server (~4-5 seconds).wrangler dev
should run locally on local assets.Describe the alternatives
Right now I'm stuck on a 500 Internal Server Error on all static resources. I'm not sure if I'm supposed to use
https://github.com/cloudflare/kv-asset-handler
locally or not or how to set it up in awrangler dev
setup. Do I have to upload the static files to KV before runningwrangler dev
?The text was updated successfully, but these errors were encountered: