When doing an extension:deploy or even fetch to a 2024.1 acct - i am now getting strange errors deploy and fetch spits out

Error Message
  Unexpected Error

when i try to set up a new token with --to, I get

(node:19213) UnhandledPromiseRejectionWarning: Error: Invalid login attempt.

at OAuth1._baseStep (/Users/gregdebres/Desktop/bbcdevscreening/ns_npm_repository/oauth1/index.js:287:19)

at processTicksAndRejections (internal/process/task_queues.js:95:5)

at async OAuth1.issueToken (/Users/gregdebres/Desktop/bbcdevscreening/ns_npm_repository/oauth1/index.js:353:38)

at async authorize (/Users/gregdebres/Desktop/bbcdevscreening/gulp/ns-deploy/net.js:333:24)

`(Use

node --trace-warnings ...

to show where the warning was created)`

(node:19213) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag

--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)`

(node:19213) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

[08:30:19] The following tasks did not complete: extension:fetch

[08:30:19] Did you forget to signal async completion?

if anyone has seen this or has any advice that would be greatly appreciated!

Token based authentication

this feature is enabled in my account im trying to deploy to and i have the .env file set up correctly too

And your .nstba file?

woah thats new to me. 😛 wheres this at ?

ill be giving that a go thanks @Steve Goldberg