Alyx

The behavior in Sequelize 7 is closer to what Sequelize-TypeScript does than Sequelize 6 (though not strictly equivalent). I'd be interested in your feedback regarding these changes in the upcoming...

I think I've finally found the solution to this problem. To bypass github's API limitations, I did the update via `git` instead of the API: https://github.com/sequelize/pr-auto-update-and-handle-conflicts/blob/74929c430b8843e691e7b83d229d8d13d78d89e3/src/action.ts#L331-L398 Feel free to copy...

It is, we try to keep our issues up-to-date as much as possible

This is something I've wanted for a while so I'll likely review it as some point. Can't promise when, work is keeping me busy again :/

Just noticed this PR is targeting `master`. We renamed the branch to `main` a little while ago. It's likely there are going to be a few merge conflicts I can...

I'm going to reopen this issue because it's not the same problem as https://github.com/sequelize/sequelize/issues/5173 and I'd rather keep them separate

Version that does not use `onload`: ```javascript function importModule(url) { // escape characters that are used to delimit the module URL. // this way the following module works: 'data:text/javascript,console.log("hello")' url...

[This PR](https://github.com/sequelize/sequelize/pull/6637) is the reason why `queryInterface.bulkInsert` is returning a single value instead of an array of values. I don't know the reasons behind it, they don't seem to be...

> Maybe if you insert a really big amount of records it might not be very feasible performance-wise to do this. The array is still created so I don't think...

@evanrittenhouse don't worry about that, you're welcome to work on things on your own terms. We appreciate the contributions nonetheless :) As for what needs to be done: that should...