Run dev against a specific config or environment
local dev
// what it does
-c picks which Wrangler config file to load when a repo has more than one; --env selects a named [env.<name>] block inside a single config along with its matching .dev.vars.<name>. Both are how you spin up the right bindings for a given project or stage.
// shell
$ wrangler dev -c ./wrangler.staging.jsonc$ wrangler dev --env staging// gotcha
-c and --env are not interchangeable — -c swaps the whole file, --env only activates a sub-block. Choose wrong and you dev with the base bindings instead of the environment's.