RealDevSquad / RealDevSquad/website-backend

Upgrade the package used in website-backend to the latest version.

Open
#2,048 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
74
Forks
276
Avg merge
1d 26m
Merged PRs (30d)
14

Description

Issue Description

The packages used in this repo are not up to the latest version staying on older package versions can lead to compatibility issues with other packages or libraries in our project. Updating your packages ensures that they work seamlessly with the latest tools and language features.

Expected Behavior

After upgrading the packages to the latest version it should not break any existing changes or lead to any unexpected error.

Current Behavior

Currently the packages are outdated and the Node version is also not upto date.

Screenshots
Reproducibility
  • This issue is reproducible
  • This issue is not reproducible
Steps to Reproduce

Check the package.json file the packages in dependencies and devDependencies of this repo, they must be upgraded to the latest version.

Severity/Priority
  • Critical
  • High
  • Medium
  • Low
Additional Information
  • These packages can be changed later again when any new and stable version is released.
  • Newer versions of packages are often more efficient and faster as compared to older versions.
  • Keeping our packages to latest version is a important part of maintaining a secure application.
Checklist
  • I have read and followed the project's code of conduct.
  • I have searched for similar issues before creating this one.
  • I have provided all the necessary information to understand and reproduce the issue.
  • I am willing to contribute to the resolution of this issue.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with package.json, reviewing the dependencies and devDependencies along with how this repository specifies its Node version. Identify the required current versions and verify that upgrading them does not introduce compatibility issues or unexpected errors; the issue does not name a test or additional entry point.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, node.js
Domain
backend
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.