Alexander Scherer

Has noone any info's on this?

@hendry91 no sadly I have not. But if you find something please keep me posted in this issue. Would really appreciate it.

Having the exact same requirement and i'm also using sequelize and sequelize-typescript

I'm having the same issue. Trying the hardest to get it resolved but can't get it working. I'm also using @nestjs/sequelize which does not make it easier because sequelize is...

> I was using `@nestjs/sequelize`. Got same error. Updating `module:es2020` and `target:es2015` to `module: commonjs` and `target: es2017` solved the issue. It does not because changes the target type to...

so there is no future for this project with the now more and more coming ESM projects?

Sadly no. And it doesn't seem like there is someone that i actively supporting this.

The workaround does not work for me sadly :/

Well now it depends, you could see it as an indicator that sequelize should take care of it and generate the uuid otherwise like in my above example it should...

in addition there could be added caching since the new function also returns an expiration date but i wanted to fix the deprecated call first