CLI Commands (@azure-net/cli)

@azure-net/cli is installed as a separate package and is versioned independently from @azure-net/kit.

Install:

npm i -D @azure-net/cli

CLI binary:

azure-net <command>

Top-level groups

• azure-net add ...
• azure-net create ...
• azure-net init ...
• azure-net install ...
• azure-net generate ...
• azure-net check ...

add

• azure-net add commit-tools
  • Installs and configures commit/lint tooling (husky, commitlint, semantic-release, etc.).
  • Option: -m, --manager <manager> (bun | pnpm | npm | yarn)

create

• azure-net create schema-factory
• azure-net create translation-manager
• azure-net create presenter-factory
• azure-net create schema-rule
• azure-net create response
• azure-net create datasource
• azure-net create datasource-provider

init

• azure-net init edges
  • Adds AzureNetPlugin to Vite config.
• azure-net init folders-structure
  • Creates project folders structure from azure-net.config.

install

• azure-net install fresh
  • Runs full bootstrap flow.
  • Creates folders structure from configured contexts.
  • Adds AzureNetPlugin to Vite config.
  • Creates src/program.ts with base createApp.
  • Then asks about optional scaffolds.

generate

• azure-net generate component
• azure-net generate widget
• azure-net generate design-component
• azure-net generate repository
• azure-net generate repo
• azure-net generate repository-method
• azure-net generate use-cases
• azure-net generate domain
• azure-net generate presenter
• azure-net generate types-json
• azure-net generate schema-from-type
• azure-net generate module
• azure-net generate module-preset

check

• azure-net check presenter-names
  • Checks duplicate presenter IDs.
• azure-net check provider-names
  • Checks duplicate createBoundaryProvider(...) IDs.
• azure-net check provider-graph
  • Checks provider dependency graph and reports provider cycles before runtime.
• azure-net check domain
  • Checks domain naming/limits/index rules. Interfaces must start with I, types must start with I or T, index.ts files must only re-exportdomain file names must not start with I.
• azure-net check imports
  • Checks that imports do not use .ts/.js extensions and that import groups are ordered as value imports, type imports, then side-effect imports.
• azure-net check hooks
  • Checks that src/hooks.server.ts/js and src/hooks.client.ts/js do not exist. Lifecycle code must live in src/program.ts; hooks are injected by AzureNetPlugin.
• azure-net check layer-imports
  • Checks forbidden imports between layers inside each context: infrastructure cannot import application/presentation, application cannot import presentation, domain cannot import application/infrastructure/presentation.
• azure-net check layer-boundaries
  • Checks cross-context alias boundary violations. Contexts may import themselves and sharedAlias. The shared context may not import other app contexts.
• azure-net check folders-structure
  • Checks allowed folders in layers, ui, ui/components.
• azure-net check internal
  • Runs all internal checks above.
• azure-net check project
  • Runs: {packageManager} run format -> azure-net check internal -> {packageManager} run lint -> {packageManager} run typecheck.
  • packageManager is read from azure-net.config.ts/js.