feat: Move javascript files to native typescript

[JPeer264]

(closes #2617)

This PR migrates all JavaScript files in the lib/ directory to native TypeScript, removing the need for JSDoc type annotations and improving type safety.

Main Changes

• Converted all .js files to .ts with proper TypeScript syntax
• Changed module system from CommonJS to ES6 modules for better TypeScript interoperability
• Updated exports to use ES6 export syntax instead of module.exports
• All types are now exported as named exports for better type inference and IDE support
• OptionsSchema is now a union to satisfy SOURCEMAPS_OPTIONS, as this one didn't had the required param
• The exports of lib/releases/options has changed its name

Breaking Changes

Module Exports

• Before: module.exports = SentryCli; (CommonJS)
• After: export class SentryCli { ... } (ES6 named export)

We could have maintained backwards compatibility with export = SentryCli;. The only problem were the types which needed to be exported as well. With ES6 named exports, we can now export all types alongside the class.

Internal Improvements

Simplified Release constructor

• Before: new Releases({ ...this.options, configFile }) - configFile was merged into options
• After: new Releases(this.options, configFile) - two separate parameters

With 2 parameters it's easier to maintain and makes the separation of concerns clearer.

[github-actions]

	Messages
📖	Do not forget to update Sentry-docs with your feature once the pull request gets approved.

Generated by 🚫 dangerJS against 5d03c1d

[cursor]

Bug: rejectOnError always rejects after resolving

When live is 'rejectOnError' and the command succeeds with exit code 0, the code resolves with 'success (live mode)' but then immediately continues to execute the reject statement because there's no return or else. This causes the promise to be settled twice and creates incorrect behavior where successful commands trigger rejection logic.

lib/helper.ts#L342-L348

sentry-cli/lib/helper.ts

Lines 342 to 348 in a8e7f1f

	pid.on('exit', (exitCode) => {
	if (live === 'rejectOnError') {
	if (exitCode === 0) {
	resolve('success (live mode)');
	}
	reject(new Error(`Command ${args.join(' ')} failed with exit code ${exitCode}`));
	}

 

---

[cursor]

Bug: SentryCli constructor breaks backwards compatibility

The constructor declares both configFile and options as required parameters without default values, but existing code calls new SentryCli() with no arguments. The original JavaScript version allowed both parameters to be optional. This breaks backwards compatibility beyond just the import syntax change documented in the CHANGELOG.

 

[cursor]

Bug: CHANGELOG contains syntax error

Line 13 contains a stray period . on its own line, appearing to be an accidental character left after editing. This creates malformed markdown in the CHANGELOG.

 

[cursor]

Bug: Undefined paramName used in non-boolean types

When OptionsSchema entries have only invertedParam without param, the paramName variable becomes undefined. For non-boolean types like string or number, line 237 concatenates undefined into the arguments array, creating invalid command-line arguments. This case needs proper handling to skip entries without a param for non-boolean types.

 

[cursor]

Bug: Required options parameter breaks backward compatibility

The new method requires the options parameter, but tests call it without arguments like releases.new('my-version'). The SentryCliReleases interface defines options as optional, and getProjectFlagsFromOptions accepts undefined with default parameter = {}. The parameter needs to be optional to match the interface and maintain backward compatibility.