Ensure v4 model compatibility with Static Web Apps

[ejizba]

This should hopefully "just work", but we should test some end-to-end static web app scenarios before GA.

[diberry]

Current issues Node JS function v4 · Issue #1139 · Azure/static-web-apps (github.com)

[ejizba]

I tried this today. I put up a PR to fix the VS Code problems here: microsoft/vscode-azurefunctions#3721

The other problem is you can't set AzureWebJobsFeatureFlags to EnableWorkerIndexing in SWA, but the flag requirement is going away - it just hasn't made it to all regions yet. I tested in West US 2 and got it working.

[offbeatful]

Nice to see some traction here! When is it expected to work without the flag?

[ejizba]

Like I said it's already rolled out in some regions - you can use "West US 2" today. For the rest of the regions, I would guess we finish in the next month or so.

[offbeatful]

Yes, I can confirm it is working in West US 2. Thank you!

[ejizba]

The flag should be enabled by default in all regions at this point

[feuersteiner]

sorry to comment here.

I am having trouble running functions v4 (typescript) with SWA cli (the cli is only compatible at node <=16, and the functions node >=18). I haven't reached the deployment problem just yet ... because the whole thing is not running on my local machine. is there a blog post on this? best practices? because for now, it feels like a little bit disorienting to not find any documentation about this transition. Thanks again for the effort!

[ejizba]

@feuersteiner I think the swa cli is supposed to work with Node18 now. See their v1.1.4 release and this issue for details. You definitely need node 18 to work with the new model, so if you can't get node 18 working with the swa cli I'd recommend following up in their repo

[feuersteiner]

@feuersteiner I think the swa cli is supposed to work with Node18 now. See their v1.1.4 release and this issue for details. You definitely need node 18 to work with the new model, so if you can't get node 18 working with the swa cli I'd recommend following up in their repo

thanks a lot for your message @ejizba !! was easy to get lost in outdated documentation (even on the site of the sea-cli stating that it only supports <=16).
Tried what you said on a fresh node 18 install and it worked like a charm 🙏🙏