Fix TS support for operators.ts

[ephys]

Pull Request Checklist

Please make sure to review and check all of these items:

• [n/a] Have you added new tests to prevent regressions?
• Does npm run test or npm run test-DIALECT pass with this change (including linting)?
• [n/a] Is a documentation update included (if this change modifies existing APIs, or introduces new ones)?
• Did you update the typescript typings accordingly (if applicable)?
• Does the description below contain a link to an existing issue (Closes #[issue]) or a description of the issue you are solving?
• Did you follow the commit message conventions explained in CONTRIBUTING.md?

Description Of Change

Closes #13791

Fix turned out more complicated than previously thought (#13797)

Current solution is definitely a hack to please both TypeScript and Node.

I think the TypeScript migration is going to keep breaking things due to how esbuild transpiles ESM. I've opened an issue regarding this as the decision will impact this PR #13806

[WikiRik]

Yeah, I'm starting to think the TypeScript migration might be better for v7. There are already various things that we've found from the conversion that we want to change and it gives a better overview to do them directly then add comments in the code that we need to refactor later. But let's discuss that at the next meeting in January; can you add things you've noticed about the migration to sequelize/meetings#6 ?

[ephys]

Oh thanks! I was looking for a place to put such a discussion and didn't think to use the meetings repo. Will do :)

[WikiRik]

@sdepold time for a 6.12.2?

[github-actions]

🎉 This PR is included in version 6.12.2 🎉

The release is available on:

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

Your semantic-release bot 📦🚀