upgraded TypeScript to 5.4.5

[VanshikaSabharwal]

What kind of change does this PR introduce?

Bugfix

Issue Number:

Fixes #2016

Did you add tests for your changes?

No

Snapshots/Videos:

Summary

This PR addresses a bug caused by an upgrade to the TypeScript version. The issue should be resolved with the updates made in this PR.
Issue#2016

Does this PR introduce a breaking change?

No

Other information

This issue arose after an automated dependabot job attempted to upgrade TypeScript from version 4.9.5 to 5.4.5, which led to failing PR tests. This PR includes the necessary updates to resolve these issues and ensure compatibility.

Have you read the contributing guide?

Yes

Summary by CodeRabbit

• New Features
  • Upgraded TypeScript version to improve type safety and introduce new language features.
• Bug Fixes
  • Resolved potential conflicts by managing TypeScript versioning in scripts.

[coderabbitai]

Caution

Review failed

The head commit changed during the review from 5ed3808 to 6f65709.

Walkthrough

The changes primarily involve upgrading the TypeScript dependency in the project from version ^4.3.5 to ^5.4.5. This upgrade aims to enhance type safety and introduce new language features. The TypeScript dependency has been removed from the main dependencies list and added to the scripts section, indicating a shift in how it will be utilized within the project.

Changes

Files	Change Summary
package.json	Updated TypeScript from ^4.3.5 to ^5.4.5 (removed from dependencies, added to scripts).

Assessment against linked issues

Objective	Addressed	Explanation
Upgrade TypeScript ( #2016 )	✅
Resolve Previous Failures ( #2016 )	❓	Unclear if past failures are resolved.
Update Codebase ( #2016 )	❌	No evidence of code modifications.
Assess Package Usage ( #2016 )	❌	No assessment of TypeScript necessity.
Documentation of Background Failures ( #2016 )	❌	No documentation referenced.

Poem

🐰 Oh, hop and skip, with joy I see,
TypeScript's fresh, as bright can be!
From four to five, we leap with glee,
New features await, just wait for me!
Code will dance, bugs will flee,
A happy codebase, full of harmony! 🌼✨

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[github-actions]

Our Pull Request Approval Process

We have these basic policies to make the approval process smoother for our volunteer team.

Testing Your Code

Please make sure your code passes all tests. Our test code coverage system will fail if these conditions occur:

1. The overall code coverage drops below the target threshold of the repository
2. Any file in the pull request has code coverage levels below the repository threshold
3. Merge conflicts

The process helps maintain the overall reliability of the code base and is a prerequisite for getting your PR approved. Assigned reviewers regularly review the PR queue and tend to focus on PRs that are passing.

Reviewers

Do not assign reviewers. Our Queue Monitors will review your PR and assign them.
When your PR has been assigned reviewers contact them to get your code reviewed and approved via:

1. comments in this PR or
2. our slack channel

Reviewing Your Code

Your reviewer(s) will have the following roles:

1. arbitrators of future discussions with other contributors about the validity of your changes
2. point of contact for evaluating the validity of your work
3. person who verifies matching issues by others that should be closed.
4. person who gives general guidance in fixing your tests

CONTRIBUTING.md

Read our CONTRIBUTING.md file. Most importantly:

1. PRs with issues not assigned to you will be closed by the reviewer
2. Fix the first comment in the PR so that each issue listed automatically closes

Other

1. 🎯 Please be considerate of our volunteers' time. Contacting the person who assigned the reviewers is not advised unless they ask for your input. Do not @ the person who did the assignment otherwise.
2. Read the CONTRIBUTING.md file make

[github-actions]

Congratulations on making your first PR! 🎊 If you haven't already, check out our Contributing Guidelines and PR Reporting Guidelines to ensure that you are following our guidelines for contributing and creating PR.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 15c8753 and f93130f.

Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

Files selected for processing (1)

• package.json (2 hunks)

Additional comments not posted (1)

package.json (1)

132-132: Confirm TypeScript is only used in development.

The TypeScript dependency has been moved from dependencies to devDependencies. Ensure that TypeScript is only used during development and is not required in production builds.

Verification successful

---

TypeScript is used only in development.

The search results indicate that TypeScript is primarily involved in development tasks, such as linting and code quality checks. This supports the decision to move TypeScript to devDependencies.

• TypeScript-related entries are found in ESLint configurations and are used with @typescript-eslint plugins, which are development tools.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify TypeScript usage in the codebase to ensure it is only used in development scripts.

# Test: Search for TypeScript usage in scripts. Expect: TypeScript should only be used in scripts related to development.
rg --type js --type ts --type json -A 5 'typescript'

Length of output: 31515

[palisadoes]

This PR has too many submitted files.

Please ensure the following:

Make your PR modifications based on the current develop branch
Submit your PRs against our develop branch.

Closing