It's getting quite large now, and seems unreasonably to load a bunch of methods into memory that are only run at startup (and most not at all, if they're older migrations).
Suggest not calling "migrate" script from main server process. Instead, add it as a separate command in the the yarn dev script, to run it before the main server process.
It's getting quite large now, and seems unreasonably to load a bunch of methods into memory that are only run at startup (and most not at all, if they're older migrations).
Suggest not calling "migrate" script from main server process. Instead, add it as a separate command in the the
yarn devscript, to run it before the main server process.