nextONazure

Contributing

Pull requests are welcome once the repository is public. Until then the maintainer works from the roadmap.

  • Run locally: build the packages and start the local stack (Azurite and the Azure Functions host)
  • Testing: unit, integration and E2E tests and the required behavioral cases
  • CI: what the GitHub Actions workflows run
  • Release: how a version is published to npm (a tag, an approval, trusted publishing)
  • Azure E2E and real Azure runs: the opt-in run against real resources, with its cost rules
  • Supply chain: audit, license check and secret scan

Ground rules

  • A behavior change needs a test in packages/tests-unit, and an E2E case if it is visible over HTTP.
  • Do not create Azure resources without agreeing on a resource group, a time window and a cost ceiling (real Azure runs).
  • The runtime .cjs files of next-on-azure must not require("node:...") (Turbopack; see Troubleshooting). ADR-0007 and ADR-0008 apply to the legacy package only.
  • Documentation is English.