Update installed, but your enviroment is still loading the outdated version

[tobkle]

Wanted to run my sandbox environment in cli shell with:

cloud

Receiving suddenly the error message:

x Update installed, but your enviroment is still loading the outdated version

tried:

npm i @serverless/cloud@latest
npm i -g  @serverless/cloud@latest
cloud update
package.json: "@serverless/cloud": "^2.7.1"

But cannot start cloud any more?

Any hints?

[eahefnawy]

do you mean that every time you run cloud you get this message? Could you let me know how you installed the CLI originally? Did you use npx by any chance? Do you use an npm package manager?

Sorry for the bombarding you with questions, I just need to understand your environment 😅

[eahefnawy]

To get around it for now, you can run with the --skip-update flag.

[tobkle]

Yes. I get this error every time, I run cloud in my first project, which was created before the last update. I get this error every time. I still get it, after even upgrading cloud as I wrote above. I installed it initially with npm i -g @serverless/cloud@latest

I don't get this error, if I start a new project from scratch with npm init cloud after the upgrade.

So I suspect any outdated remainings in my first project.

I use:

which cloud
~/.nvm/versions/node/v16.14.0/bin/cloud

The solution for me at the moment is:

cloud --skip-update

With that it is working again in my first pre-update project.

Even more interesting is, after having run cloud --skip-update once, it even works again with only cloud. This is great. But I have no idea why.

Thank you. I'm able to continue now.

[dougmoscrop]

Sorry about this, Tobias! We are working on making the auto-update process more robust, as well as improving the instructions if it encounters a problem.

[tobkle]

Don't mind, that work-around with --skip-update is fine for me.