Skip to content

Add Azure Function backend for server-side TCP ping timing - #1

Merged
juusimaa merged 2 commits into
mainfrom
feature/azure-functions-ping
Aug 18, 2026
Merged

Add Azure Function backend for server-side TCP ping timing#1
juusimaa merged 2 commits into
mainfrom
feature/azure-functions-ping

Conversation

@juusimaa

Copy link
Copy Markdown
Owner

Replaces the browser's opaque no-cors fetch timing with a real /api/ping Azure Function that times a TCP handshake to the target host and returns readable JSON, deployed as a managed function inside the existing Static Web App. Adds a local dev workflow via swa start + func start.

Jouni Uusimaa and others added 2 commits August 18, 2026 06:56
Replaces the browser's opaque no-cors fetch timing with a real /api/ping
Azure Function that times a TCP handshake to the target host and returns
readable JSON, deployed as a managed function inside the existing Static
Web App. Adds a local dev workflow via swa start + func start.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Azure's Oryx build validates a file literally named
staticwebapp.config.json somewhere under app_location. With
@azure/static-web-apps-cli installed as a root devDependency, its
own bundled JSON schema file (node_modules/@azure/static-web-apps-cli/
schema/staticwebapp.config.json, 21.7KB) got swept up by that scan
during CI's npm install and rejected for exceeding Azure's 20KB
config-file limit.

swa-cli is only needed for local dev, so run it via npx instead of
keeping it in package.json/node_modules — dev:full now points at an
independently-running `func start` via --api-devserver-url.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@juusimaa
juusimaa merged commit 7f93674 into main Aug 18, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant