🐛 BUG: npm start after forced login results in a lot of warnings

[jkup]

What version of Wrangler are you using?

0.0.0-8f7ac7b

What operating system are you using?

Mac

Describe the Bug

I installed wrangler@alpha and then ran an init followed by npm start. I wasn't logged in so I was bounced to the login flow and after I authenticated I got a bunch of terminal spam even though it was a brand new project. Here is my terminal output.

☁ npm install -g wrangler@alpha

added 46 packages, and audited 47 packages in 6s

found 0 vulnerabilities
☁  wrangler --version
0.0.0-8f7ac7b
☁  wrangler init test
 ⛅️ wrangler 0.0.0-8f7ac7b
---------------------------
Using npm as package manager.
✨ Successfully created wrangler.toml
No package.json found. Would you like to create one? (y/n)

added 46 packages, and audited 47 packages in 1s

found 0 vulnerabilities
✨ Created package.json
Would you like to use TypeScript? (y/n)

added 2 packages, and audited 49 packages in 3s

found 0 vulnerabilities
✨ Created tsconfig.json, installed @cloudflare/workers-types into devDependencies
Would you like to create a Worker at src/index.ts? (y/n)
✨ Created src/index.ts

To start developing your Worker, run `cd test && npm start`
To publish your Worker to the Internet, run `npm run publish`
☁  cd test
☁  npm start

> [email protected] start
> wrangler dev

 ⛅️ wrangler 0.0.0-8f7ac7b
---------------------------
It looks like you have used Wrangler 1's `config` command to login with an API token.
This is no longer supported in the current version of Wrangler.
If you wish to authenticate via an API token then please set the `CLOUDFLARE_API_TOKEN` environment variable.
Attempting to login via OAuth...
Successfully logged in.
It looks like you have used Wrangler 1's `config` command to login with an API token.
This is no longer supported in the current version of Wrangler.
If you wish to authenticate via an API token then please set the `CLOUDFLARE_API_TOKEN` environment variable.
It looks like you have used Wrangler 1's `config` command to login with an API token.
This is no longer supported in the current version of Wrangler.
If you wish to authenticate via an API token then please set the `CLOUDFLARE_API_TOKEN` environment variable.
It looks like you have used Wrangler 1's `config` command to login with an API token.
This is no longer supported in the current version of Wrangler.
If you wish to authenticate via an API token then please set the `CLOUDFLARE_API_TOKEN` environment variable.
⬣ Listening at http://localhost:8787
It looks like you have used Wrangler 1's `config` command to login with an API token.
This is no longer supported in the current version of Wrangler.
If you wish to authenticate via an API token then please set the `CLOUDFLARE_API_TOKEN` environment variable.
It looks like you have used Wrangler 1's `config` command to login with an API token.
This is no longer supported in the current version of Wrangler.
If you wish to authenticate via an API token then please set the `CLOUDFLARE_API_TOKEN` environment variable.
It looks like you have used Wrangler 1's `config` command to login with an API token.
This is no longer supported in the current version of Wrangler.
If you wish to authenticate via an API token then please set the `CLOUDFLARE_API_TOKEN` environment variable.
It looks like you have used Wrangler 1's `config` command to login with an API token.
This is no longer supported in the current version of Wrangler.
If you wish to authenticate via an API token then please set the `CLOUDFLARE_API_TOKEN` environment variable.
It looks like you have used Wrangler 1's `config` command to login with an API token.
This is no longer supported in the current version of Wrangler.
If you wish to authenticate via an API token then please set the `CLOUDFLARE_API_TOKEN` environment variable.
waiting for connection...
waiting for connection...
╭────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ B to open a browser, D to open Devtools, L to turn on local mode, X to exit                                            │
╰────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯

[jkup]

Worth noting:

1. After ctrl+c'ing the process and running wrangler dev again it worked without errors
2. I'm only 2/3 being able to reproduce this

[petebacondarwin]

Oh!! Haha, we don't re-read the config file once the login has occurred, so we don't realise that it has changed.

[petebacondarwin]

Luckily we even have a helper for that, which was only being used in the tests so far: reinitialiseAuthTokens().