hana-developer-cli-tool-example typescript-configuration.instructions.md

Development rules for TypeScript configuration files such as tsconfig.json. TypeScript configuration controls how code is checked, compiled, and supplied with generated type declarations.

In plain words
What is it for?
Use them when changing compiler options, ESM module resolution, strict checking, declaration files, source maps, incremental builds, path aliases, or separate build configurations.
Why use it?
They prevent incompatible module settings and inconsistent type checking across a project that mixes JavaScript and TypeScript. They also standardize debugging and build behavior.

Instructions file for GitHub Copilot

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add instructions/sap-samples/hana-developer-cli-tool-example/typescript-configuration
Clone the repo
git clone --depth 1 https://github.com/SAP-samples/hana-developer-cli-tool-example

Made for: GitHub Copilot.

Per session 4,270 This file is loaded in full into every session.
When invoked 4,270 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.04270 $0.04270
Opus 5 $0.02135 $0.02135
Sonnet 5 $0.00854 $0.00854
Haiku 4.5 $0.00427 $0.00427

Measured 2d ago against content hash 56cc25271371, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

hana-developer-cli-tool-example typescript-configuration.instructions.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.github/instructions/typescript-configuration.instructions.md · 655 lines

How it starts

The opening of the file, as written. The whole thing — 655 lines — stays where its author put it; the contents beside it link to each section on GitHub.

TypeScript Configuration Guidelines

Use this guide when creating or modifying TypeScript configuration files (tsconfig.json) in the project.

Scope and Purpose

This guide applies to TypeScript configuration in:

  • Root tsconfig.json - Type generation from JavaScript sources
  • mcp-server/tsconfig.json - TypeScript source compilation
  • Subdirectory-specific TypeScript configs
  • Build-specific TypeScript configs (e.g., tsconfig.build.json)

Critical Principles

  1. Dual Config Strategy: Root config for type generation, subproject configs for compilation
  2. ESM Compatibility: Use Node16/NodeNext module resolution for ESM projects
  3. Strict Mode: Enable strict type checking for maximum safety
  4. Declaration Files: Generate .d.ts files for external consumption
  5. Source Maps: Enable source maps for debugging compiled code
  6. Incremental Builds: Use incremental compilation for faster rebuilds
  7. Path Mappings: Configure path aliases for clean imports
  8. Type-Only Imports: Use "importsNotUsedAsValues": "error" to enforce type-only imports

Root Configuration Pattern (Type Generation from JS)

Pattern: Generate Types from JavaScript Sources

This project uses JavaScript with JSDoc comments for the main CLI. TypeScript is configured to extract type definitions:

{
  "compilerOptions": {
    // Enable type checking and declaration generation from JS
    "allowJs": true,                    // Process .js files
    "checkJs": true,                    // Type-check .js files
    "declaration": true,                // Generate .d.ts files
    "emitDeclarationOnly": true,        // ONLY generate declarations
    
    // Module system
    "module": "ESNext",                 // Use latest ECMAScript modules
    "moduleResolution": "node",         // Node.js style resolution
    "target": "ES2022",                 // Modern JavaScript features
    
    // Output configuration
    "outDir": "./types",                // Type declarations go here
    "rootDir": ".",                     // Source root
    
    // Type checking strictness
    "strict": false,                    // Lenient for JS sources
    "noImplicitAny": false,             // Allow implicit any in JS
    "strictNullChecks": false,          // No null checks for JS
    
    // Other options
    "esModuleInterop": true,            // CommonJS/ESM interop
    "skipLibCheck": true,               // Skip library type checks
    "forceConsistentCasingInFileNames": true,
    "resolveJsonModule": true           // Import JSON files
  },
  
  "include": [
    "bin/**/*.js",
    "routes/**/*.js",
    "utils/**/*.js",
    "index.js"
  ],
  
  "exclude": [
    "node_modules",
    "tests",
    "coverage",
    "types",
    "**/*.test.js",
    "**/*.Test.js"
  ]
}

Read the full file on GitHub · 655 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 655 lines · 4,270 tokens per session scan A 56cc25271371

Subscribe to this mod's changes

hana-developer-cli-tool-example typescript-configuration.instructions.md is an instructions file published in the GitHub repository SAP-samples/hana-developer-cli-tool-example (109 stars, last pushed 7d ago), licensed Apache-2.0. It adds 4,270 tokens to every session, about $0.0214 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.