feat: Remove generateTsConfig option from ts-proto module

[connerohnesorge]

Summary

Removes the generateTsConfig configuration option from the ts-proto language module as part of architectural cleanup (Spectr change: remove-ts-proto-generatetsconfig).

Why This Change

The generateTsConfig option violated architectural principles by:

• Scope mismatch: Configuration belongs with source code, not generated code
• Poor defaults: Generic template doesn't adapt to project-specific needs
• Maintenance burden: Unnecessary configuration option with low utility
• Better alternatives: Modern options (protobuf-es) eliminate the need

What Changed

• ✅ Removed conditional generateTsConfig block from src/languages/js/ts-proto.nix (lines 88-109)
• ✅ Option definition already removed from src/lib/bufrnix-options.nix in previous work
• ✅ Converted tasks.md to tasks.jsonc for better Spectr task tracking
• ✅ Added documentation comments explaining project-managed configuration

Breaking Change

Yes - This removes a public configuration option. Users who rely on generateTsConfig = true will need to:

• Remove that line from their Nix configuration
• Create their own tsconfig.json in their project root if needed
• Or use protobuf-es as the modern recommended approach

Impact

• Low impact: Option was disabled by default (false)
• No example usage: No examples in the repository use this option
• Migration path: Simple removal or manual tsconfig.json creation

Test Plan

• All 39 examples pass (./test-examples.sh)
• Quick validation passes (./check-examples.sh)
• No generation errors in ts-proto examples
• Code formatting validated (nix fmt)
• Linting passes (lint)
• Spectr validation passes (spectr validate remove-ts-proto-generatetsconfig)
• All TypeScript/JavaScript examples work correctly without the option:
  • js-example, js-es-custom-outputpath, js-grpc-web
  • js-annotations, js-protovalidate, ts-flake-parts
  • multilang-per-files (TypeScript frontend)

Migration Guide

Before (will no longer work):

tsProto = {
  enable = true;
  generateTsConfig = true;
};

After (recommended):

# Option 1: Create tsconfig.json in your project root
tsProto = {
  enable = true;
};

# Option 2: Use modern protobuf-es instead
es = {
  enable = true;
  target = "ts";
};

Related

• Related change: remove-es-generatepackagejson (similar cleanup for protobuf-es)
• Spectr proposal: spectr/changes/remove-ts-proto-generatetsconfig/proposal.md

🤖 Generated with Claude Code