Hello @mchotti
We have noticed this bug when using the older sqlite3 package in v4.3.7+ versions. We are going to add a migration guide about this but you can switch your sqlite3 package for better-sqlite3 as mentioned at the end of this issue. #14193
- Replace
sqlite3forbetter-sqlite3in yourpackage.json.
Thank you for reaching out!