/opt/node_app/index.js
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:815:15)
at Function.Module._load (internal/modules/cjs/loader.js:667:27)
at Module.require (internal/modules/cjs/loader.js:887:19)
at require (internal/modules/cjs/helpers.js:74:18)
at module.exports (/opt/node_app/lib/setup/sockets.js:15:30)
at Object. (/opt/node_app/lib/server.js:47:12)
at Module._compile (internal/modules/cjs/loader.js:999:30)
at Object.Module._extensions…js (internal/modules/cjs/loader.js:1027:10)
at Module.load (internal/modules/cjs/loader.js:863:32)
at Function.Module._load (internal/modules/cjs/loader.js:708:14) {
code: ‘MODULE_NOT_FOUND’,
requireStack: [
‘/opt/node_app/lib/setup/sockets.js’,
‘/opt/node_app/lib/server.js’,
‘/opt/node_app/index.js’
The “lib” folder in the root of your node project. Those are the Server Connect system files and will be regenerated with the latest one on a save of server action.
Given that deleting the SC lib folder or the AC folders are quite often suggested as a solution for out-of-sync core file issues maybe you guys want to streamline this into it’s own button “Rebuild framework files” or similar which will do exactly the same but without calling it “Delete a folder and everything will be solved” slight_smile:
This is not common any more - only if you were upgrading from very old version.
Most issues we have tackled already in the new Project Assets Updater.
Still improving and adding stuff thought, more cooperation with git reverts as well maybe also adding updates checks for third party custom extensions.
Maybe also a force rebuild all framework files is a handy option, but we rather have it fully work so it is not needed.