❌ Error al importar/iniciar la aplicación: Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'express' imported from /home/fzdcxdef/dcompras.ingresomedia.com/server/index_sqlite.js
    at packageResolve (node:internal/modules/esm/resolve:873:9)
    at moduleResolve (node:internal/modules/esm/resolve:946:18)
    at defaultResolve (node:internal/modules/esm/resolve:1188:11)
    at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:642:12)
    at #cachedDefaultResolve (node:internal/modules/esm/loader:591:25)
    at ModuleLoader.resolve (node:internal/modules/esm/loader:574:38)
    at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:236:38)
    at ModuleJob._link (node:internal/modules/esm/module_job:130:49) {
  code: 'ERR_MODULE_NOT_FOUND'
}
ERROR CRÍTICO AL INICIAR: Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'express' imported from /home/fzdcxdef/dcompras.ingresomedia.com/server/index_sqlite.js
    at packageResolve (node:internal/modules/esm/resolve:873:9)
    at moduleResolve (node:internal/modules/esm/resolve:946:18)
    at defaultResolve (node:internal/modules/esm/resolve:1188:11)
    at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:642:12)
    at #cachedDefaultResolve (node:internal/modules/esm/loader:591:25)
    at ModuleLoader.resolve (node:internal/modules/esm/loader:574:38)
    at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:236:38)
    at ModuleJob._link (node:internal/modules/esm/module_job:130:49) {
  code: 'ERR_MODULE_NOT_FOUND'
}
[2025-12-18T23:00:02.103Z] [PID: 2330675] [32m[NODE-CRON][32m [33m[WARN][0m missed execution at Fri Dec 19 2025 00:00:00 GMT+0100 (Central European Standard Time)! Possible blocking IO or high CPU user at the same process used by node-cron.
[2025-12-21T05:00:03.418Z] [PID: 2048554] [32m[NODE-CRON][32m [33m[WARN][0m missed execution at Sun Dec 21 2025 06:00:00 GMT+0100 (Central European Standard Time)! Possible blocking IO or high CPU user at the same process used by node-cron.
[2025-12-21T23:00:01.105Z] [PID: 2279028] [32m[NODE-CRON][32m [33m[WARN][0m missed execution at Mon Dec 22 2025 00:00:00 GMT+0100 (Central European Standard Time)! Possible blocking IO or high CPU user at the same process used by node-cron.
Error checking ML availability: fetch failed
Error checking ML availability: fetch failed
Error checking ML availability: fetch failed
Error checking ML availability: fetch failed
Error checking ML availability: fetch failed
Error checking ML availability: fetch failed
Error checking ML availability: fetch failed
Error checking ML availability: fetch failed
Error checking ML availability: fetch failed
Error checking ML availability: fetch failed
[2025-12-23T05:00:02.454Z] [PID: 2279379] [32m[NODE-CRON][32m [33m[WARN][0m missed execution at Tue Dec 23 2025 06:00:00 GMT+0100 (Central European Standard Time)! Possible blocking IO or high CPU user at the same process used by node-cron.
[2025-12-24T11:00:01.005Z] [PID: 2279028] [32m[NODE-CRON][32m [33m[WARN][0m missed execution at Wed Dec 24 2025 12:00:00 GMT+0100 (Central European Standard Time)! Possible blocking IO or high CPU user at the same process used by node-cron.
[2025-12-25T17:00:01.113Z] [PID: 2279379] [32m[NODE-CRON][32m [33m[WARN][0m missed execution at Thu Dec 25 2025 18:00:00 GMT+0100 (Central European Standard Time)! Possible blocking IO or high CPU user at the same process used by node-cron.
[2025-12-26T05:00:02.608Z] [PID: 2279379] [32m[NODE-CRON][32m [33m[WARN][0m missed execution at Fri Dec 26 2025 06:00:00 GMT+0100 (Central European Standard Time)! Possible blocking IO or high CPU user at the same process used by node-cron.
[2025-12-27T05:00:01.916Z] [PID: 2279379] [32m[NODE-CRON][32m [33m[WARN][0m missed execution at Sat Dec 27 2025 06:00:00 GMT+0100 (Central European Standard Time)! Possible blocking IO or high CPU user at the same process used by node-cron.
[2025-12-27T05:00:03.945Z] [PID: 2279028] [32m[NODE-CRON][32m [33m[WARN][0m missed execution at Sat Dec 27 2025 06:00:00 GMT+0100 (Central European Standard Time)! Possible blocking IO or high CPU user at the same process used by node-cron.
[2025-12-29T05:00:01.644Z] [PID: 2279379] [32m[NODE-CRON][32m [33m[WARN][0m missed execution at Mon Dec 29 2025 06:00:00 GMT+0100 (Central European Standard Time)! Possible blocking IO or high CPU user at the same process used by node-cron.
[2025-12-30T05:00:01.731Z] [PID: 2279379] [32m[NODE-CRON][32m [33m[WARN][0m missed execution at Tue Dec 30 2025 06:00:00 GMT+0100 (Central European Standard Time)! Possible blocking IO or high CPU user at the same process used by node-cron.
[2025-12-30T05:00:02.938Z] [PID: 2279028] [32m[NODE-CRON][32m [33m[WARN][0m missed execution at Tue Dec 30 2025 06:00:00 GMT+0100 (Central European Standard Time)! Possible blocking IO or high CPU user at the same process used by node-cron.
[2026-01-01T05:00:01.176Z] [PID: 2279379] [32m[NODE-CRON][32m [33m[WARN][0m missed execution at Thu Jan 01 2026 06:00:00 GMT+0100 (Central European Standard Time)! Possible blocking IO or high CPU user at the same process used by node-cron.
[2026-01-01T05:00:02.452Z] [PID: 2279028] [32m[NODE-CRON][32m [33m[WARN][0m missed execution at Thu Jan 01 2026 06:00:00 GMT+0100 (Central European Standard Time)! Possible blocking IO or high CPU user at the same process used by node-cron.
[2026-01-02T05:00:01.054Z] [PID: 2279028] [32m[NODE-CRON][32m [33m[WARN][0m missed execution at Fri Jan 02 2026 06:00:00 GMT+0100 (Central European Standard Time)! Possible blocking IO or high CPU user at the same process used by node-cron.
[2026-01-02T05:00:01.701Z] [PID: 2279379] [32m[NODE-CRON][32m [33m[WARN][0m missed execution at Fri Jan 02 2026 06:00:00 GMT+0100 (Central European Standard Time)! Possible blocking IO or high CPU user at the same process used by node-cron.
[2026-01-04T05:00:02.417Z] [PID: 2279379] [32m[NODE-CRON][32m [33m[WARN][0m missed execution at Sun Jan 04 2026 06:00:00 GMT+0100 (Central European Standard Time)! Possible blocking IO or high CPU user at the same process used by node-cron.
[2026-01-05T05:00:01.012Z] [PID: 2279028] [32m[NODE-CRON][32m [33m[WARN][0m missed execution at Mon Jan 05 2026 06:00:00 GMT+0100 (Central European Standard Time)! Possible blocking IO or high CPU user at the same process used by node-cron.
[2026-01-05T05:00:01.403Z] [PID: 2279379] [32m[NODE-CRON][32m [33m[WARN][0m missed execution at Mon Jan 05 2026 06:00:00 GMT+0100 (Central European Standard Time)! Possible blocking IO or high CPU user at the same process used by node-cron.
[2026-01-06T05:00:01.439Z] [PID: 2279379] [32m[NODE-CRON][32m [33m[WARN][0m missed execution at Tue Jan 06 2026 06:00:00 GMT+0100 (Central European Standard Time)! Possible blocking IO or high CPU user at the same process used by node-cron.
[2026-01-06T05:00:01.886Z] [PID: 2279028] [32m[NODE-CRON][32m [33m[WARN][0m missed execution at Tue Jan 06 2026 06:00:00 GMT+0100 (Central European Standard Time)! Possible blocking IO or high CPU user at the same process used by node-cron.
[2026-01-08T05:00:01.830Z] [PID: 2279028] [32m[NODE-CRON][32m [33m[WARN][0m missed execution at Thu Jan 08 2026 06:00:00 GMT+0100 (Central European Standard Time)! Possible blocking IO or high CPU user at the same process used by node-cron.
[2026-01-08T05:00:02.084Z] [PID: 2279379] [32m[NODE-CRON][32m [33m[WARN][0m missed execution at Thu Jan 08 2026 06:00:00 GMT+0100 (Central European Standard Time)! Possible blocking IO or high CPU user at the same process used by node-cron.
[2026-01-10T05:00:02.085Z] [PID: 2279028] [32m[NODE-CRON][32m [33m[WARN][0m missed execution at Sat Jan 10 2026 06:00:00 GMT+0100 (Central European Standard Time)! Possible blocking IO or high CPU user at the same process used by node-cron.
[2026-01-10T05:00:02.798Z] [PID: 2279379] [32m[NODE-CRON][32m [33m[WARN][0m missed execution at Sat Jan 10 2026 06:00:00 GMT+0100 (Central European Standard Time)! Possible blocking IO or high CPU user at the same process used by node-cron.
[2026-01-11T05:00:01.319Z] [PID: 2279379] [32m[NODE-CRON][32m [33m[WARN][0m missed execution at Sun Jan 11 2026 06:00:00 GMT+0100 (Central European Standard Time)! Possible blocking IO or high CPU user at the same process used by node-cron.
[2026-01-11T05:00:02.012Z] [PID: 2279028] [32m[NODE-CRON][32m [33m[WARN][0m missed execution at Sun Jan 11 2026 06:00:00 GMT+0100 (Central European Standard Time)! Possible blocking IO or high CPU user at the same process used by node-cron.
[2026-01-12T11:00:02.487Z] [PID: 2857019] [32m[NODE-CRON][32m [33m[WARN][0m missed execution at Mon Jan 12 2026 12:00:00 GMT+0100 (Central European Standard Time)! Possible blocking IO or high CPU user at the same process used by node-cron.
[2026-01-15T05:00:02.048Z] [PID: 2857019] [32m[NODE-CRON][32m [33m[WARN][0m missed execution at Thu Jan 15 2026 06:00:00 GMT+0100 (Central European Standard Time)! Possible blocking IO or high CPU user at the same process used by node-cron.
[2026-01-16T05:00:02.600Z] [PID: 2857019] [32m[NODE-CRON][32m [33m[WARN][0m missed execution at Fri Jan 16 2026 06:00:00 GMT+0100 (Central European Standard Time)! Possible blocking IO or high CPU user at the same process used by node-cron.
[2026-01-19T23:00:01.006Z] [PID: 3066316] [32m[NODE-CRON][32m [33m[WARN][0m missed execution at Tue Jan 20 2026 00:00:00 GMT+0100 (Central European Standard Time)! Possible blocking IO or high CPU user at the same process used by node-cron.
[2026-01-20T23:00:02.542Z] [PID: 3066316] [32m[NODE-CRON][32m [33m[WARN][0m missed execution at Wed Jan 21 2026 00:00:00 GMT+0100 (Central European Standard Time)! Possible blocking IO or high CPU user at the same process used by node-cron.
[2026-01-22T05:00:02.418Z] [PID: 3066316] [32m[NODE-CRON][32m [33m[WARN][0m missed execution at Thu Jan 22 2026 06:00:00 GMT+0100 (Central European Standard Time)! Possible blocking IO or high CPU user at the same process used by node-cron.
[2026-01-22T05:00:02.442Z] [PID: 3067175] [32m[NODE-CRON][32m [33m[WARN][0m missed execution at Thu Jan 22 2026 06:00:00 GMT+0100 (Central European Standard Time)! Possible blocking IO or high CPU user at the same process used by node-cron.
[2026-01-23T05:00:03.035Z] [PID: 3067175] [32m[NODE-CRON][32m [33m[WARN][0m missed execution at Fri Jan 23 2026 06:00:00 GMT+0100 (Central European Standard Time)! Possible blocking IO or high CPU user at the same process used by node-cron.
