Starting with --local then turning off local mode crashes

[geelen]

Since you're never prompted to login & choose your accountId, you don't get that nor apitToken in the session, and you get this error

❯ npx wrangler dev index.js --local
⎔ Starting a local server...
⬣ Listening at http://localhost:8787

  ERROR  accountId is required

 node_modules/wrangler/wrangler-dist/index_node.js:98573:29

 98570:   }, []);
 98571: }
 98572: function Remote(props) {
 98573:   (0, import_assert.default)(props.accountId, "accountId is required");
 98574:   (0, import_assert.default)(props.apiToken, "apiToken is required");
 98575:   const token = useWorker({
 98576:     name: props.name,

 - Remote (node_modules/wrangler/wrangler-dist/index_node.js:98573:29)
 - renderWithHooks (node_modules/wrangler/wrangler-dist/index_node.js:18265:26)
 - mountIndeterminateComponent (node_modules/wrangler/wrangler-dist/index_node.js:20385:21)
 - beginWork (node_modules/wrangler/wrangler-dist/index_node.js:21172:22)
 - Object.invokeGuardedCallbackProd (node_modules/wrangler/wrangler-dist/index_node.js:22163:19)
 - invokeGuardedCallback (node_modules/wrangler/wrangler-dist/index_node.js:22250:39)
 - beginWork$1 (node_modules/wrangler/wrangler-dist/index_node.js:25088:15)
 - performUnitOfWork (node_modules/wrangler/wrangler-dist/index_node.js:24314:20)
 - workLoopSync (node_modules/wrangler/wrangler-dist/index_node.js:24265:13)
 - renderRootSync (node_modules/wrangler/wrangler-dist/index_node.js:24240:15)

⎔ Shutting down local server.

[threepointone]

A similar problem when passing --host, or routes, is that the zone id won't be available when starting from local and moving to remote mode.

[valgaze]

Steps

mkdir sampleworker
cd sampleworker
npx wrangler@2 init -y
npx wrangler@2 dev --local
# press l

• Node v16.7 // npm 7.20.3
• Wrangler v2

Error

accountId is required
node_modules/wrangler/wrangler-dist/cli.js:108881:35

If it needs an account id, maybe should error out if wrangler.toml is missing account_id per https://developers.cloudflare.com/workers/wrangler/configuration/

[sdarnell]

Note that this is still an issue with version 2.0.7, and even if I previously logged in with wranger, AND actually specify an account_id in the wrangler.toml file (I also tried accountId).