Allow uppercase letters in package names

[bengotow]

Summary

Updated the package name validation regex to accept uppercase letters (A-Z) in addition to lowercase letters, allowing for more flexible package naming conventions.

Changes

• Modified VALID_PACKAGE_NAME regex pattern from /^[a-z0-9._-]+$/ to /^[a-zA-Z0-9._-]+$/ in app/src/package.ts
• Updated error messages in app/src/package.ts and app/src/package-manager.ts to reflect the new validation pattern

Details

This change relaxes the package naming constraints to permit camelCase and PascalCase naming conventions, which are common in JavaScript/TypeScript ecosystems. The validation now accepts:

• Lowercase letters (a-z)
• Uppercase letters (A-Z)
• Numbers (0-9)
• Dots, underscores, and hyphens (._-)

Error messages have been updated to accurately reflect the new validation requirements.

https://claude.ai/code/session_01CeqkQ4HBGw1rYVtx83hcfB

[indent-staging]

PR Summary

Widens the plugin/theme package.json#name validation regex to also accept uppercase ASCII letters, restoring compatibility with previously-installed packages (e.g. MyTheme) that broke after the path-traversal hardening in #2698. The path-traversal protections are preserved — [a-zA-Z0-9._-] still excludes path separators, whitespace, and ../., and the path.resolve equality check in installPackageFromPath remains intact.

• app/src/package.ts: VALID_PACKAGE_NAME changed from /^[a-z0-9._-]+$/ to /^[a-zA-Z0-9._-]+$/; InvalidPackageNameError message updated to match.
• app/src/package-manager.ts: user-facing error message in installPackageFromPath updated to quote the new regex.

Issues

No issues found.

CI Checks

All CI checks passed on commit 518be75.

Custom Rules 3 rules evaluated, 3 passed, 0 failed

This is a longer title to see what happens when they are too long to fit
B
Ben Rule