Upgrade package typescript from 4.9.5 to 5.4.5

[palisadoes]

Rationale

1. This was previously attempted by the automated dependabot job but the PR tests failed.
2. This issue has been created to fix the issue as there may be multiple dependency requirements that need updating

This is a major revision upgrade and many files may need to be updated to the new syntax, functions, methods and classes

Task

1. Upgrade package typescript from 4.9.5 to 5.4.5
2. Remove this package if it is:
   1. unused
   2. unnecessary. For example:
      1. the functionality can be maintained by using another package we are already using,
      2. If we are using only one function or class in the package you can consider replacing it with code that resides in this repository
      3. It is used by a feature that the end user is unlikely to ever use

Background Failing PRs

• chore(deps): bump typescript from 4.9.5 to 5.4.5 #2014
• https://github.com/PalisadoesFoundation/talawa-admin/actions/runs/9247355671/job/25436082785?pr=2014
• https://github.com/PalisadoesFoundation/talawa-admin/actions/runs/9247355543/job/25436082385?pr=2014

Release Note Details

Bumps typescript from 4.9.5 to 5.4.5.

Release notes

Sourced from typescript's releases.

TypeScript 5.4.5

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

• fixed issues query for Typescript 5.4.0 (Beta).
• fixed issues query for Typescript 5.4.1 (RC).
• fixed issues query for Typescript 5.4.2 (Stable).
• fixed issues query for Typescript 5.4.3 (Stable).
• fixed issues query for Typescript 5.4.4 (Stable).
• fixed issues query for Typescript 5.4.5 (Stable).

Downloads are available on:

• NuGet package

TypeScript 5.4.4

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

• fixed issues query for Typescript 5.4.0 (Beta).
• fixed issues query for Typescript 5.4.1 (RC).
• fixed issues query for Typescript 5.4.2 (Stable).
• fixed issues query for Typescript 5.4.3 (Stable).
• fixed issues query for Typescript 5.4.4 (Stable).

Downloads are available on:

• NuGet package

TypeScript 5.4.3

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

• fixed issues query for Typescript 5.4.0 (Beta).
• fixed issues query for Typescript 5.4.1 (RC).
• fixed issues query for Typescript 5.4.2 (Stable).
• fixed issues query for Typescript 5.4.3 (Stable).

Downloads are available on:

• NuGet package

TypeScript 5.4

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

... (truncated)

Commits

• 27bcd4c Update LKG
• 9f33bf1 🤖 Pick PR #58098 (Fix constraints of nested homomorph...) into release-5.4 (#...
• 71b2f84 Bump version to 5.4.5 and LKG
• 892936f 🤖 Pick PR #58083 (Don't propagate partial union/inter...) into release-5.4 (#...
• 38a7c05 release-5.4: Always set node-version for setup-node (#58117)
• b754fc3 🤖 Pick PR #57778 (fix type import check for default-i...) into release-5.4 (#...
• 8eb3367 Bump version to 5.4.4 and LKG
• de9096b 🤖 Pick PR #57871 (Divide-and-conquer strategy for int...) into release-5.4 (#...
• 06aae98 🤖 Pick PR #57973 (Compare package.json paths with cor...) into release-5.4 (#...
• 6d8134e 🤖 Pick PR #57637 (Fixed a regression related to deter...) into release-5.4 (#...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[github-actions]

This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue.

[MadhaneeswaranP]

Can I take this issue? @palisadoes

[github-actions]

This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue.

[palisadoes]

Unassigning no activity

[Spoorthy1423]

Hey!! @palisadoes , i would like to work on this issue, please assign me

[varshith257]

@Spoorthy1423 You need to get assigned the issue first and submit a PR. Hope you can remind and abide this rule from next time which is one of our community guidelines

[github-actions]

This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue.

[Cioppolo14]

Unassigning due to no activity or PR.

[ManjariRathore]

Hello @Cioppolo14 @palisadoes
I would like to work on this issue, if possible can you assign this to me. I will raise a draft PR asap.

[Cioppolo14]

@ManjariRathore you are requesting to work on many issues. You can only be assigned 2 at a time. Please indicate which 2 are your priorities. Thank you.

[VanshikaSabharwal]

@palisadoes kindly assign me this issue

[VanshikaSabharwal]

@varshith257 I have created pull request regarding this issue. Can you please have a look at it. [https://github.com//pull/2207]

[varshith257]

@VanshikaSabharwal Follow this #2208 (comment)

If you face any difficult reach out me in Slack

[VanshikaSabharwal]

@VanshikaSabharwal Follow this #2208 (comment)

If you face any difficult reach out me in Slack

okay @varshith257

[github-actions]

This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue.

[palisadoes]

Unassigning. Inactivity

[adithyanotfound]

Please assign

[adithyanotfound]

CRA (create-react-app) only supports up to TypeScript version 4.9.5. For better TypeScript compatibility and potential performance benefits, migrating to Vite or preferably Next.js is recommended. If you want me to migrate to Vite please assign Issue #1864.

NOTE: Migrating to Vite may introduce a few issues in deployment that you'll need to address. For now, you could continue using CRA and wait for a future update that supports newer TypeScript versions.

[palisadoes]

OK. We are using vite in the API. So there is precedent. We need the consistency.