Steved
Steved
CDCloudflare Developers
Created by Vero on 10/13/2023 in #wrangler
Wrangler DX feedback
There are a few commands that don't have --local options. For example, wrangler d1 create,wrangler d1 list, wrangler d1 delete all could have --local equivalents. wrangler d1 execute has --local, but it isn't documented (https://developers.cloudflare.com/workers/wrangler/commands/#execute) Having local and remote consistency increases confidence - who likes testing on production resources. wrangler d1 migrations create - isn't clear how to create migrations locally. Shouldn't be dependent on a database name? (if so why?) Wrangler occasionally forces authentication, even though it is operating entirely locally. This is confusing/worrying if you're trying to do something local.
C3 offers to deploy the empty project. Whilst this might seem a neat idea, it is likely to put the willies up most people who just want to try something out (locally). Better to just explain how to deploy when they get to that point. Improved SSL support, allowing an external key/cert to be specified - i.e. one that is trusted, rather than the wrangler one that isn't. wrangler.toml => .json (TOML just causes too much confusion IMHO). Better clarity on local pages dev and bindings. I spent ages trying to sort out sveltekit, and now have a solution, but others are likely to have issues. There's no explanation of what the wrangler pages dev -- cmd actually does, and whether it should really help.
8 replies