Compile
apache/skywalking-nodejs
Compile / build / type-check the skywalking-nodejs agent. An agent skill from apache/skywalking-nodejs.
Repository-specific Azure Functions Node.js Host-worker architecture and change-validation workflow.
Install Azure Functions Node Worker
$ npx skills add Azure/azure-functions-nodejs-worker --skill azure-functions-node-worker -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Azure/azure-functions-nodejs-worker azure-functions-node-worker --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Azure/azure-functions-nodejs-worker.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/azure-functions-node-worker .claude/skills/azure-functions-node-worker && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "azure-functions-node-worker" agent skill from https://github.com/Azure/azure-functions-nodejs-worker/tree/v3.x/.github/skills/azure-functions-node-worker into .claude/skills/azure-functions-node-worker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azure-functions-node-worker", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Azure/azure-functions-nodejs-worker/tree/v3.x/.github/skills/azure-functions-node-workerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Azure/azure-functions-nodejs-worker --skill azure-functions-node-worker -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Azure/azure-functions-nodejs-worker azure-functions-node-worker --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Azure/azure-functions-nodejs-worker.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/azure-functions-node-worker .agents/skills/azure-functions-node-worker && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "azure-functions-node-worker" agent skill from https://github.com/Azure/azure-functions-nodejs-worker/tree/v3.x/.github/skills/azure-functions-node-worker into .agents/skills/azure-functions-node-worker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azure-functions-node-worker", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Azure/azure-functions-nodejs-worker --skill azure-functions-node-worker -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Azure/azure-functions-nodejs-worker azure-functions-node-worker --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Azure/azure-functions-nodejs-worker.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/azure-functions-node-worker .cursor/skills/azure-functions-node-worker && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "azure-functions-node-worker" agent skill from https://github.com/Azure/azure-functions-nodejs-worker/tree/v3.x/.github/skills/azure-functions-node-worker into .cursor/skills/azure-functions-node-worker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azure-functions-node-worker", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Azure/azure-functions-nodejs-worker.git --path .github/skills/azure-functions-node-worker--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Azure/azure-functions-nodejs-worker --skill azure-functions-node-worker -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Azure/azure-functions-nodejs-worker azure-functions-node-worker --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Azure/azure-functions-nodejs-worker.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/azure-functions-node-worker .gemini/skills/azure-functions-node-worker && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "azure-functions-node-worker" agent skill from https://github.com/Azure/azure-functions-nodejs-worker/tree/v3.x/.github/skills/azure-functions-node-worker into .gemini/skills/azure-functions-node-worker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azure-functions-node-worker", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Azure/azure-functions-nodejs-worker azure-functions-node-workerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Azure/azure-functions-nodejs-worker --skill azure-functions-node-worker -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Azure/azure-functions-nodejs-worker.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/azure-functions-node-worker .github/skills/azure-functions-node-worker && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "azure-functions-node-worker" agent skill from https://github.com/Azure/azure-functions-nodejs-worker/tree/v3.x/.github/skills/azure-functions-node-worker into .github/skills/azure-functions-node-worker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azure-functions-node-worker", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Azure/azure-functions-nodejs-worker --skill azure-functions-node-worker -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Azure/azure-functions-nodejs-worker azure-functions-node-worker --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Azure/azure-functions-nodejs-worker.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/azure-functions-node-worker .opencode/skills/azure-functions-node-worker && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "azure-functions-node-worker" agent skill from https://github.com/Azure/azure-functions-nodejs-worker/tree/v3.x/.github/skills/azure-functions-node-worker into .opencode/skills/azure-functions-node-worker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azure-functions-node-worker", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
azure-functions-node-worker- GitHub stars
- 110
- Token cost
- ~2.1k tokens
- SKILL.md length
- 927 words
- Files
- 2 (incl. references)
- Skills in repo
- 3
- Repo updated
- First seen
- Licence
- MIT
At a glance
Repository-specific Azure Functions Node.js Host-worker architecture and change-validation workflow.
- Works in 5 steps: Classify the Change → Trace the Owning Path → Preserve Domain Invariants → …
- Every implementation
- SKILL.md covers Core Model, Required Workflow, Change-to-Validation Matrix and Boundaries
- Calls npm and npx
What it does
Azure Functions Node Worker is an agent skill from Azure/azure-functions-nodejs-worker, published by the product's own GitHub organization. Repository-specific Azure Functions Node.js Host-worker architecture and change-validation workflow. Use for every implementation, fix, refactor, test, or explanation involving this repository, especially worker startup, gRPC StreamingMessage handling, initialization, specialization, metadata/indexing, function loading and invocation, programming models, hooks, converters, logging, process lifecycle, Node.js behavior, protobuf, build, or tests. Validate each code change against Host compatibility and Node runtime…
Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/architecture.md`).
It sits in Backend & APIs, covering gRPC and Protobuf. It works with Azure Functions, gRPC and Node.js. The repository describes itself as: The Node.js worker for the Azure Functions runtime - https://functions.azure.com. The licence is MIT.
When your agent uses it
- Every implementation
- Explanation involving this repository
- Especially worker startup
- GRPC StreamingMessage handling
Example prompts
- “/azure-functions-node-worker”
Requirements
- Node.js
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 8c3b7f3. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
npmnpx
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm and npx, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Azure Functions Node Worker loads about 2.1k tokens when it runs, and up to ~4.8k if it reads all its reference files. Until then it costs about 140 tokens; SKILL.md has 927 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Azure/azure-functions-nodejs-worker at commit 8c3b7f3, republished under its MIT licence (© Azure). 927 words, ~2,077 tokens.
Download SKILL.mdSave it as
.claude/skills/azure-functions-node-worker/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- azure-functions-node-worker
- description
- Repository-specific Azure Functions Node.js Host-worker architecture and change-validation workflow. Use for every implementation, fix, refactor, test, or explanation involving this repository, especially worker startup, gRPC StreamingMessage handling, initialization, specialization, metadata/indexing, function loading and invocation, programming models, hooks, converters, logging, process lifecycle, Node.js behavior, protobuf, build, or tests. Validate each code change against Host compatibility and Node runtime invariants.
- argument-hint
- [change, file, or behavior]
Azure Functions Node.js Worker
Apply this skill to code changes in this repository. It supplies domain context and a mandatory validation workflow; it does not replace focused security analysis or required human review.
Read architecture.md before reasoning about behavior that crosses the Host-worker boundary or more than one lifecycle stage.
Core Model
Treat this repository as the process boundary between the Azure Functions Host and a user's Node.js function application:
src/nodejsWorker.tsenters the worker andsrc/Worker.tsparses Host-provided startup arguments.src/GrpcClient.tscreates the bidirectional gRPC stream.src/setupEventStream.tsroutes HostStreamingMessagerequests to event handlers and constructs protocol responses.- Initialization or specialization loads the function app and establishes process-wide state in
WorkerContextandAppContext. - Metadata/load handlers select worker indexing or legacy Host indexing.
InvocationHandlerbridges RPC data to the active@azure/functionsprogramming model, runs hooks, invokes user code, and converts the response.- Termination runs app hooks, closes the stream, and exits the process.
The Host, worker, programming model, and function app are separate compatibility surfaces. Do not reason about one in isolation when a change crosses their boundary.
Required Workflow
1. Classify the Change
Identify all affected surfaces before editing:
- Host RPC contract or message routing
- worker startup, state, or lifecycle
- function app discovery or module loading
- programming model or core API bridge
- invocation bindings or typed-data conversion
- hooks, logging, errors, or diagnostics
- Node.js runtime, event loop, environment, working directory, or process exit
- generated protobuf, packaging, dependencies, or release configuration
If any critical path is affected, also load azure-functions-node-worker-critical-path. If data crosses a trust boundary, executable content is loaded, credentials may be exposed, or dependencies change, also load azure-functions-node-worker-security.
2. Trace the Owning Path
Start at the code that directly decides behavior. Trace only the relevant path:
Host input -> StreamingMessage -> handler -> worker/app state or programming model -> response/log/side effect
State the local invariant being preserved and a cheap test that could falsify the proposed behavior. Do not edit generated rpc.js, rpc_static.js, or rpc.d.ts directly. Protocol changes start in azure-functions-language-worker-protobuf/src/proto/ and regenerate outputs with npm run gen.
3. Preserve Domain Invariants
For every change, verify the applicable invariants:
- Every handled request retains its
requestId, expected response property, andStatusResultsemantics. - Handler failures are returned through the common event-stream error path; host-bound error text remains sanitized.
setupEventStream()andsetupCoreModule()are established before user app code depends on them.- Worker state is process-wide. Specialization resets app state without accidentally reinitializing the worker identity or stream.
- Worker indexing and legacy Host indexing remain distinct; registration locks are not weakened.
- Invocation input/output conversion remains symmetric with the programming-model contract.
- Pre- and post-invocation hooks retain ordering and documented mutation behavior.
- User code loading preserves CommonJS and ESM behavior, package
mainhandling, retry behavior, and entry-point error policy. - Code does not assume gRPC requests or invocations are serialized. Avoid blocking the Node.js event loop and unbounded synchronous work.
- Changes to
process.env,process.cwd(), module caches, listeners, timers, and process exit account for process-wide effects and test cleanup. - Logs keep system/user category semantics and do not bypass error or secret sanitization.
- Generated protocol outputs match their
.protosources and are reviewed as generated artifacts.
Show full SKILL.md (407 more words)Show less
4. Implement and Test the Behavior
Keep the change at the owning abstraction. Add or update the nearest test that observes the externally meaningful result, not only an internal call.
Use the test map in architecture.md. Prefer the smallest executable check first, for example:
npx mocha -r ts-node/register "test/Worker.test.ts"
npx mocha -r ts-node/register "test/eventHandlers/InvocationHandler.test.ts"Then run the checks required by the affected surface:
npm run lint
npm test
npm run buildnpm run build regenerates protobuf outputs before compiling. Inspect those generated changes and do not accept unrelated churn.
Run npm run host-sanity for changes to startup arguments, gRPC behavior, protocol routing, worker configuration, module loading, or Host compatibility when the adjacent Host repository and prerequisites are available. Report clearly when that integration check cannot run.
5. Report Validation
Do not say a change is validated without executable evidence. Report:
- the invariant tested
- the exact focused and broad checks run
- pass/fail results
- checks not run and why
- whether security analysis or human review is required
Do not treat lint, compilation, snapshots, or generated-code verification alone as behavioral validation.
Change-to-Validation Matrix
| Changed surface | Minimum focused validation | Broader validation |
|---|---|---|
Worker.ts, GrpcClient.ts, startup | test/Worker.test.ts, test/GrpcClient.test.ts as applicable | lint, full tests, build; Host sanity for contract changes |
setupEventStream.ts, event handlers | matching test/eventHandlers/*.test.ts | lint, full tests, build |
startApp.ts, package parsing, script loading | test/startApp.test.ts, test/parsers/parsePackageJson.test.ts, or test/loadScriptFile.test.ts | lint, full tests, build |
| invocation, hooks, converters | test/eventHandlers/InvocationHandler.test.ts plus a focused regression | lint, full tests, build |
| reload or process state | test/eventHandlers/FunctionEnvironmentReloadHandler.test.ts with state cleanup assertions | lint, full tests, build |
| termination | test/eventHandlers/terminateWorker.test.ts | lint, full tests, build |
| errors, logging, sanitization | test/errors.test.ts or nearest handler test | lint, full tests, build; security skill |
| blocked event loop or runtime versions | test/blockMonitorTest.ts or test/utils.test.ts | lint, full tests, build |
.proto or generated RPC files | regenerate with npm run gen, focused handler/converter tests | lint, full tests, build, generated diff review, Host sanity |
| dependency, bundle, or packaging files | focused startup/load test | lint, full tests, build, webpack; security and human review |
Boundaries
- Do not infer Azure Functions Host behavior solely from worker code. If compatibility depends on unspecified Host behavior, identify the assumption and require Host documentation, Host source, or an integration test.
- Do not "fix" intentional execution of function app code as though it were arbitrary code execution. The worker exists to load and run that code; security findings must show an unintended boundary expansion.
- Do not hand-edit generated protobuf outputs.
- Do not silently broaden supported Node.js versions, protocol fields, capabilities, or programming-model behavior.
- Do not claim approval for a critical-path change. Produce validation evidence and hand it to the required human reviewer.
© Azure, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (references) in .github/skills/azure-functions-node-worker of Azure/azure-functions-nodejs-worker.
- SKILL.md
- references/architecture.md
Open the folder on GitHubat commit 8c3b7f3
Compare with similar skills
Azure Functions Node Worker next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Azure Functions Node Worker this skillAzure/azure-functions-nodejs-worker | 110 | — | ~2.1k | Automated safety check: Pass | MIT | |
| Compileapache/skywalking-nodejs | 180 | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Fishjam JS Server SDKsoftware-mansion-labs/skills | 291 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Adding Personhog RpcPostHog/posthog | 40k | — | ~2.1k | Automated safety check: Pass | Custom licence | |
| Cortexdb Memory Openclawliliang-cn/cortexdb | 274 | — | ~1.6k | Automated safety check: Pass | MIT | |
| Use Yaakmountain-loop/yaak | 19k | — | ~1.9k | Automated safety check: Pass | MIT |
Similar skills
Fishjam JS Server SDK
software-mansion-labs/skills
Node.js / TypeScript server SDK for Fishjam — backends that create rooms, mint peer tokens, listen to server notifications, and run agents.
- Official
Adding Personhog Rpc
PostHog/posthog
Guide for adding a new RPC to personhog-replica and personhog-router.
Cortexdb Memory Openclaw
liliang-cn/cortexdb
Give a Node.js agent (such as OpenClaw) durable, local-first memory plus a queryable SPARQL knowledge graph, backed by CortexDB through its gRPC sidecar and the cortexdb-client npm package.
Use Yaak
mountain-loop/yaak
A skill your agent uses when the user mentions Yaak, a Yaak workspace, or the yaak command, or asks to call, hit, or smoke test HTTP/REST endpoints, save or organize API requests for reuse or manual…
Golang Pro
antoniopaya22/go-rest-template
Implements concurrent Go patterns using goroutines and channels, designs and builds microservices with gRPC or REST, optimizes Go application performance with pprof, and enforces idiomatic Go with…
More from Azure/azure-functions-nodejs-worker
- Official
Azure Functions Node Worker Critical Path
Azure/azure-functions-nodejs-worker
Mandatory human-intervention gate for critical Azure Functions Node.js worker code.
- Official
Azure Functions Node Worker Security
Azure/azure-functions-nodejs-worker
Security analysis for the Azure Functions Node.js worker. An agent skill from Azure/azure-functions-nodejs-worker.
Related
Works with
Categories
Questions about Azure Functions Node Worker
What does Azure Functions Node Worker do?
Repository-specific Azure Functions Node.js Host-worker architecture and change-validation workflow. Azure Functions Node Worker is an agent skill from Azure/azure-functions-nodejs-worker, published by the product's own GitHub organization.js Host-worker architecture and change-validation workflow.
When should I use Azure Functions Node Worker?
Azure Functions Node Worker fits situations like: every implementation; explanation involving this repository; especially worker startup; GRPC StreamingMessage handling.
How do I install Azure Functions Node Worker in Claude Code?
Run `npx skills add Azure/azure-functions-nodejs-worker --skill azure-functions-node-worker -a claude-code`. Or copy the skill folder (.github/skills/azure-functions-node-worker in Azure/azure-functions-nodejs-worker) into .claude/skills/azure-functions-node-worker in your project. Claude Code loads it when a task matches its description.
How do I install Azure Functions Node Worker in Codex?
Run `npx skills add Azure/azure-functions-nodejs-worker --skill azure-functions-node-worker -a codex`. Or copy the skill folder (.github/skills/azure-functions-node-worker in Azure/azure-functions-nodejs-worker) into .agents/skills/azure-functions-node-worker in your project. Codex loads it when a task matches its description.
Can I use Azure Functions Node Worker in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Azure/azure-functions-nodejs-worker --skill azure-functions-node-worker -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/azure-functions-node-worker, .gemini/skills/azure-functions-node-worker, .github/skills/azure-functions-node-worker and .opencode/skills/azure-functions-node-worker in your project.
What does Azure Functions Node Worker need to run?
Going by SKILL.md and its folder, Azure Functions Node Worker needs the command-line tools its instructions call (npm and npx). Our summary lists: Node.js.
Does Azure Functions Node Worker access the network?
SKILL.md contains no URLs. Its commands use npm and npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Azure Functions Node Worker safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Azure Functions Node Worker use?
Azure Functions Node Worker is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Azure Functions Node Worker use?
About 2.1k tokens (SKILL.md is roughly 8.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.7k tokens, read only when the agent opens those files.
What are the alternatives to Azure Functions Node Worker?
Skills that share tags, products or a category with Azure Functions Node Worker: Compile (apache/skywalking-nodejs, 180 stars), Fishjam JS Server SDK (software-mansion-labs/skills, 291 stars), Adding Personhog Rpc (PostHog/posthog, 40k stars) and Cortexdb Memory Openclaw (liliang-cn/cortexdb, 274 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Azure Functions Node Worker?
Azure (a GitHub organization, an official publisher) maintains it in Azure/azure-functions-nodejs-worker, which has 110 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 8, 2026.
Source: Azure/azure-functions-nodejs-worker on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.