Slash-graphql CLI: Could not get device code from Auth0 on `slash-graphql login`

[jdgamble555 (Jonathan Gamble)]

If you never created a password in the first place, you have to use “forgot my password” to create one.

I feel like this is bad security since the terminal log can store your username and password in one command. It seems the entire token command should be updated if you can no longer use it.

Also, there are still other slash-graphql errors that need to be looked at:

Error when trying to use CLI to update Lambdas

I am having this same problem: npm i -g slash-graphql then slash-graphql login MYEMAIL MYPASSWORD then slash-graphql update-lambda -e MYENDPOINT -f MY-LAMBDAS-JSFILE and I get this error: TypeError: first argument must be a string or instance of Error So I try logging out like so: slash-graphql logout and I get this: Error: Could not log you out. Please try logging in with `slash-graphql login`, then try invalidating all clients with `slash-graphql logout -a so I try that: slash-g…

Using Slash GraphQL CLI in Deployment without Login

I get the same. When I login using a different account from the backend I’m trying to update, I get: Error: Cannot find backend <backend-url>

Slash GraphQL CLI Error on Update-Lambda

I am trying to upload my lambda script to Slash using the following command: slash-graphql update-lambda -e <endpoint> -f=lambdas.js -t <key> And I am getting this error: TypeError: first argument must be a string or instance of Error I tried logging out and back in and I upgraded slash-graphql to 1.18.0 and I still get the same error. Seems to be related to the recent slash updates. Any thoughts?

J