Typescript 5.2 support

[esetnik]

Issue Creation Checklist

• I understand that my issue will be automatically closed if I don't fill in the requested information
• I have read the contribution guidelines

Feature Description

Describe the feature you'd like to see implemented

node_modules/sequelize/types/transaction.d.ts:121:13 - error TS2395: Individual declarations in merged declaration 'LOCK' must be all exported or all local

Describe why you would like this feature to be added to Sequelize

The latest version of typescript 5.2 was released and sequelize is not compatible

Is this feature dialect-specific?

• No. This feature is relevant to Sequelize as a whole.
• Yes. This feature only applies to the following dialect(s):

Would you be willing to resolve this issue by submitting a Pull Request?

• Yes, I have the time and I know how to start.
• Yes, I have the time but I will need guidance.
• No, I don't have the time, but my company or I are supporting Sequelize through donations on OpenCollective.
• No, I don't have the time, and I understand that I will need to wait until someone from the community or maintainers is interested in implementing my feature.

---

Indicate your interest in the addition of this feature by adding the 👍 reaction. Comments such as "+1" will be removed.

[WikiRik]

You're quick! I'm assuming this is for v6 right? Since our typing tests for main pass for TypeScript 5.2 (see #16412 )

[esetnik]

Yes, for v6 👍 . I see that it is already fixed in v7 alpha.

[WikiRik]

I just noticed that you're willing to submit a PR, go for it! Do also update the following line to include 4.9, 5.0, 5.1 and 5.2;

sequelize/.github/workflows/ci.yml

Line 39 in e4c780c

ts-version: ["4.1", "4.2", "4.3", "4.4", "4.5", "4.6", "4.7", "4.8"]

[esetnik]

@WikiRik do you plan to release more versions of v6 if I am able to fix the issue?

[WikiRik]

@WikiRik do you plan to release more versions of v6 if I am able to fix the issue?

Yes, every merged PR towards the v6 branch triggers a release

[avifatal]

Hi,
This is my package.json:

 "dependencies": 
    "@nestjs/common": "10.1.3",
    "@nestjs/config": "^3.0.0",
    "@nestjs/core": "10.1.3",
    "@nestjs/sequelize": "^10.0.0",
    "sequelize-typescript": "^2.1.5",
    "sequelize": "^6.32.1",

  },
  "devDependencies": {
    "typescript": "^5.2.0"
  }

how can I resolve for now the error...
becuse "typescript": "^5.1.0" also fails.
Thaks

[Marocco2]

Hi, This is my package.json:

 "dependencies": 
    "@nestjs/common": "10.1.3",
    "@nestjs/config": "^3.0.0",
    "@nestjs/core": "10.1.3",
    "@nestjs/sequelize": "^10.0.0",
    "sequelize-typescript": "^2.1.5",
    "sequelize": "^6.32.1",

  },
  "devDependencies": {
    "typescript": "^5.2.0"
  }

how can I resolve for now the error... becuse "typescript": "^5.1.0" also fails. Thaks

set "typescript": "==5.1.0"
then switch back to "typescript": "^5.2.0" only when issue is resolved

[abdullateef97]

Hi, This is my package.json:

 "dependencies": 
    "@nestjs/common": "10.1.3",
    "@nestjs/config": "^3.0.0",
    "@nestjs/core": "10.1.3",
    "@nestjs/sequelize": "^10.0.0",
    "sequelize-typescript": "^2.1.5",
    "sequelize": "^6.32.1",

  },
  "devDependencies": {
    "typescript": "^5.2.0"
  }

how can I resolve for now the error... becuse "typescript": "^5.1.0" also fails. Thaks

set "typescript": "==5.1.0" then switch back to "typescript": "^5.2.0" only when issue is resolved

this doesn't work for me

[alejoiglesias]

Hi, This is my package.json:

 "dependencies": 
    "@nestjs/common": "10.1.3",
    "@nestjs/config": "^3.0.0",
    "@nestjs/core": "10.1.3",
    "@nestjs/sequelize": "^10.0.0",
    "sequelize-typescript": "^2.1.5",
    "sequelize": "^6.32.1",

  },
  "devDependencies": {
    "typescript": "^5.2.0"
  }

how can I resolve for now the error... becuse "typescript": "^5.1.0" also fails. Thaks

set "typescript": "==5.1.0" then switch back to "typescript": "^5.2.0" only when issue is resolved

this doesn't work for me

"typescript": "5.1.6" works for me

[abdullateef97]

thank you @alejoiglesias this works fine

[esetnik]

This should be fixed once #16442 gets merged and a new v6 release is published

[github-actions]

🎉 This issue has been resolved in version 6.33.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[mat813]

6.33.0 fixes it for me.