npm errors on start with prod docker image

[focusaurus]

I have latest trunk code and re-pulled the prod reaction base docker image. I think this maybe hasn't been developed yet as there's a related issue in #28 so are you all so far still running with a dev image some how? The docker base prod image can't really be used directly, it needs be be built on top of with app-specific npm deps and source code.

╰○ dc up                                                                             b: trunk s: clean
Starting federated-gateway_gateway_1 ... done
Attaching to federated-gateway_gateway_1
gateway_1  | fix-volumes: Fixing all volumes to be owned by '1000:1000'
gateway_1  | fix-volumes: Skipping volume /app. Already owned by 1000:1000
gateway_1  | fix-volumes: Skipping volume /app/node_modules. Already owned by 1000:1000
gateway_1  | Running 'npm run start' as user node in Docker container...
gateway_1  |
gateway_1  | > [email protected] start /app
gateway_1  | > node --experimental-modules --experimental-json-modules src/index.js
gateway_1  |
gateway_1  | (node:34) ExperimentalWarning: The ESM module loader is experimental.
gateway_1  | internal/modules/esm/default_resolve.js:84
gateway_1  |   let url = moduleWrapResolve(specifier, parentURL);
gateway_1  |             ^
gateway_1  |
gateway_1  | Error: Cannot find package 'envalid' imported from /app/src/config.js
gateway_1  |     at Loader.resolve [as _resolve] (internal/modules/esm/default_resolve.js:84:13)
gateway_1  |     at Loader.resolve (internal/modules/esm/loader.js:73:33)
gateway_1  |     at Loader.getModuleJob (internal/modules/esm/loader.js:147:40)
gateway_1  |     at ModuleWrap.<anonymous> (internal/modules/esm/module_job.js:41:40)
gateway_1  |     at link (internal/modules/esm/module_job.js:40:36) {
gateway_1  |   code: 'ERR_MODULE_NOT_FOUND'
gateway_1  | }
gateway_1  | npm ERR! code ELIFECYCLE
gateway_1  | npm ERR! errno 1
gateway_1  | npm ERR! [email protected] start: `node --experimental-modules --experimental-json-modules src/index.js`
gateway_1  | npm ERR! Exit status 1
gateway_1  | npm ERR!
gateway_1  | npm ERR! Failed at the [email protected] start script.
gateway_1  | npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
gateway_1  |
gateway_1  | npm ERR! A complete log of this run can be found in:
gateway_1  | npm ERR!     /home/node/.npm/_logs/2020-03-05T00_27_27_549Z-debug.log
federated-gateway_gateway_1 exited with code 1