InstructionMITv1.0.0awesome-copilot
azure-functions-typescript
TypeScript patterns for Azure Functions
At a glance
- Kind
- Instruction · Ananke
prompt - Reference
awesome-copilot/azure-functions-typescript·ananke://prompt/awesome-copilot/azure-functions-typescript@1.0.0- Applies to
**/*.ts, **/*.js, **/*.json- Files
- 1 · 817 B
- How it's used
- Instructions apply automatically to files matching their applyTo glob in GitHub Copilot. For Claude Code, reference the file from CLAUDE.md.
Upstream metadata
applyTo | **/*.ts, **/*.js, **/*.json |
|---|
Documentation
View upstream ↗Guidance for Code Generation
- Generate modern TypeScript code for Node.js
- Use
async/awaitfor asynchronous code - Whenever possible, use Node.js v22 LTS built-in modules instead of external packages
- Always use Node.js async functions, like
node:fs/promisesinstead offsto avoid blocking the event loop - Ask before adding any extra dependencies to the project
- The API is built using Azure Functions using
@azure/functions@4package. - Each endpoint should have its own function file, and use the following naming convention:
src/functions/<resource-name>-<http-verb>.ts - When making changes to the API, make sure to update the OpenAPI schema (if it exists) and
README.mdfile accordingly.