Vite + React Build and Deploy job github action cannot create certificate during 'vite build'. (failed to load config from /github/workspace/vite.config.js)

[travisrbe]

I am trying to deploy a site to Azure static web apps.

I used the Azure portal to create a new Static Web App, and configured the portal options to use my github repo as shown here:

As expected, upon creation of the resource in Azure, a workflow yml file was automatically generated in GitHub, and the job ran but failed.

(I ran into an issue with Node versioning, but was able to resolve that error by being explicit in my package.json file.)

During the Build and Deploy step, I am getting the following error message:

failed to load config from /github/workspace/vite.config.js
error during build:
Error: Could not create certificate.
at file:///github/workspace/vite.config.js.timestamp-1711659903508-baa8584510e9a.mjs:27:11
(...at etc...)

The portion of the vite.config.js file throwing this error (out-of-the-box code):

const baseFolder =
env.APPDATA !== undefined && env.APPDATA !== ''
? ${env.APPDATA}/ASP.NET/https
: ${env.HOME}/.aspnet/https;

const certificateName = "MyAppName";
const certFilePath = path.join(baseFolder, ${certificateName}.pem);
const keyFilePath = path.join(baseFolder, ${certificateName}.key);

if (!fs.existsSync(certFilePath) || !fs.existsSync(keyFilePath)) {
if (0 !== child_process.spawnSync('dotnet', [
'dev-certs',
'https',
'--export-path',
certFilePath,
'--format',
'Pem',
'--no-password',
], { stdio: 'inherit', }).status) {
throw new Error("Could not create certificate.");
}
}

I threw in a couple of logging messages to check that the certFilePath value was being generated in a sane way - looks fine to me but I don't know for certain that it is correct. It's showing: /github/home/.aspnet/https/MyAppName.pem - is this right?

Can anyone tell me either why this is happening, or how I can debug this issue?

[JasonETucker]

I have the same problem here as well

[PocPhot]

I have the same problem
Have you solved that problem yet?

[travisrbe]

No. :(