Skip to content

Serverless CLI always fails with "exit status 243" #13121

@iknowcss-invenco

Description

@iknowcss-invenco

Issue description

Whenever I run a Serverless CLI command, I get the exact same behaviour. For example:

sls -v

This starts by running an update:

⠋ Updating

...before failing with the following to stdout:

Error: exit status 243

Previously I set-up npm to install global node modules to a proper system lib directory, so I had to run sudo npm i -g .... But given that the sls CLI tool insists on doing an upgrade every time, I switched it to install globals to ~/.npm-global so sudo is not necessary anymore. However, even though I can install without sudo and am definitely running sls from the new directory (which sls yields /Users/XXX/.npm-global/bin/sls), I get the same error.

The biggest difficulty I have is that there is no meaningful output from the CLI tool for me to diagnose and fix the issue myself. I'm completely stuck.

Happy to provide any additional info. Hopefully anyone else getting the same error code can find this thread with Google now.

Edit:

After a bit more sleuthing, I can trace the problem to the execution of the binary itself. sls -v translates to:

/Users/XXX/.npm-global/lib/node_modules/serverless/node_modules/.bin/serverless-darwin-arm64-0.0.2 -v

When I run that directly I get the same behaviour:

  1. ⠋ Updating
  2. Error: exit status 243

I'm running on a Nov 2024 MacBook Pro which is arm64 architecture.

Context

Not available as I cannot run any CLI commands successfully.

However, when I cat /Users/XXX/.npm-global/lib/node_modules/serverless/package.json I can see the version installed is 4.19.1.

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions