Azure / Azure/static-web-apps-cli

Error message unclear when trying to deploy a Function with unsupported Node version

Open
#821 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
668
Forks
156
PR merge metrics
No merged PRs in 30d

Description

Before filing this issue, please ensure you're using the latest CLI by running `swa --version` and comparing to the latest version on [npm](https://www.npmjs.com/package/@azure/static-web-apps-cli).

**Are you accessing the CLI from the default port `:4280` ?**

- [ ] No, I am using a different port number (`--port`) and accessing the CLI from that port
- [x] Yes, I am accessing the CLI from port `:4280`

> Make sure you are accessing the URL printed in the console when running `swa start`!

**ℹ️ NOTE: Make sure to enable debug logs when running any `swa` commands using `--verbose=silly`**

**Describe the bug**
My SWA project was set to use Node.js runtime v20 (unsupported, but I didn't know that at the time) in the `swa-cli.config.json` file.

When trying to deploy, you get this message:
image

Even though both parameter are defined in the config. Same occurs when specifying the parameters as CLI flags.

The real issue is that the Node.js version set is unsupported, but the error is captured and wrongly reported by SWA CLI.

**To Reproduce**
Init a new SWA project, and set "apiVersion" to 20 in "swa-cli.config.json"

**Expected behavior**
Error reports clearly that runtime is unsupported.(it seems the error is properly reported by the StaticSiteClient, but not surfaced)

**Desktop (please complete the following information):**

- OS: MacOS
- Version14.4

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.