[WIP] Update dependencies in package.json and package-lock.json

[Copilot]

Thanks for asking me to work on this. I will get started on it and keep this PR's description up to date as I form a plan and make progress.

Original prompt

Update all dependencies in package.json and package-lock.json to their latest safe versions, covering both security-related and general outdated packages. Ensure all direct and indirect dependencies are updated, including those listed in devDependencies and overrides. After the update, ensure all scripts (linting, tests, build) are still passing. If any major version breaks the build/test, provide minimal necessary code or config changes to restore compatibility with new versions. Commit and document all changes clearly.

The following is the prior conversation context from the user's chat exploration (may be truncated):

User: Update (@update) security issues or fix outdated versions

Assistant: You'd like to update security issues or fix outdated versions in the TLMSLLC/wallet-contract-v5 repository, specifically referencing Dependabot alert ton-blockchain#62. To proceed, I'll need to:

1. Identify the exact dependency and issue highlighted by alert کلاهبردار ton-blockchain/wallet-contract-v5#62.
2. Locate the affected files (likely a package.json, package-lock.json, yarn.lock, or requirements file).
3. Update the dependency to a secure or latest version.
4. Commit changes and (optionally) open a Pull Request for the update.

Let me start by finding the details of Dependabot alert ton-blockchain#62 in TLMSLLC/wallet-contract-v5.

Assistant: You have requested to update security issues or fix outdated versions in the repository TLMSLLC/wallet-contract-v5, referring to Dependabot alert ton-blockchain#62.

Current Dependency Overview

The repository uses a package.json and package-lock.json with the following (partial) devDependencies, which could trigger Dependabot alerts if any have vulnerabilities or are outdated:

{
  "devDependencies": {
    "@ton/blueprint": "^0.21.0",
    "@ton/core": "^0.56.3",
    "@ton/crypto": "^3.2.0",
    "@ton/sandbox": "^0.20.0",
    "@ton/test-utils": "^0.4.2",
    "@types/jest": "^29.5.0",
    "@types/node": "^20.2.5",
    "@typescript-eslint/eslint-plugin": "^5.38.1",
    "@typescript-eslint/parser": "^5.38.1",
    "eslint": "8.22.0",
    "eslint-config-airbnb-typescript": "^17.0.0",
    "eslint-config-prettier": "^8.5.0",
    "eslint-plugin-import": "^2.26.0",
    "eslint-plugin-prettier": "^4.2.1",
    "eslint-plugin-unused-imports": "^2.0.0",
    "jest": "^29.7.0",
    "prettier": "^2.8.6",
    "ton": "~13.6.0",
    "ts-jest": "^29.0.5",
    "ts-node": "^10.9.1",
    "typescript": "^5.5.2"
  }
}

Next Steps

To fix outdated or vulnerable dependencies:

1. Update dependencies:

   • Run npm outdated to see which packages are outdated.
   • Run npm audit to check for vulnerabilities.
   • Run npm update to update all packages where appropriate.
   • For major version updates, check CHANGELOGs for breaking changes and update your code as necessary.

2. Manually update versions in package.json for any risky/outdated/vulnerable dependencies flagged by Dependabot and run:

   npm install
   

3. Commit the updated package.json and package-lock.json files.

4. Test your code to make sure everything still works (run lint, tests, build, etc).

5. Push and create a PR.

---

Would you like me to automatically prepare a pull request that updates all dependencies to their latest safe versions (major & minor), or only target a specific (known vulnerable) package if you know which one is in alert ton-blockchain#62?

Please specify if you want:

• Only security/vulnerability fixes?
• All dependencies updated to latest versions?
• Both security and general updates?

Let me know your preference!

User: both security and general please

Assistant: I am preparing a pull request to update all dependencies in TLMSLLC/wallet-contract-v5 for both security vulnerabilities and general outdated versions, including any required adjustments for compatibility.

This pull request was created from Copilot chat.

[Copilot]

Copilot wasn't able to review any files in this pull request.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Lawrence Lucas Large (LukeLarge)]

[WIP] Update dependencies in package.json and package-lock.json
#19

has read only permissions

[Copilot]

Copilot wasn't able to review any files in this pull request.