[examples/hackernews] Example is broken.

[beauby]

$ docker compose build
...
 => ERROR [reactive_cache 6/6] RUN npm run build                                                                                                                                                                                                                                                                          1.8s
------
 > [reactive_cache 6/6] RUN npm run build:
0.202 
0.202 > reactive-hackernews@1.0.0 build
0.202 > tsc
0.202 
1.803 src/hackernews.service.ts(5,3): error TS2305: Module '"@skipruntime/api"' has no exported member 'Values'.
1.803 src/hackernews.service.ts(84,17): error TS7006: Parameter 'a' implicitly has an 'any' type.
1.803 src/hackernews.service.ts(84,20): error TS7006: Parameter 'b' implicitly has an 'any' type.
1.803 src/hackernews.service.ts(85,23): error TS7006: Parameter 'p' implicitly has an 'any' type.
------
failed to solve: process "/bin/sh -c npm run build" did not complete successfully: exit code: 2

[beauby]

Bumping @skipruntime/server version to 0.0.6 fixes the build:

index ca2e91061..9af4a753e 100644
--- a/examples/hackernews/reactive_service/package.json
+++ b/examples/hackernews/reactive_service/package.json
@@ -10,7 +10,7 @@
   "description": "",
   "dependencies": {
     "postgres": "^3.4.5",
-    "@skipruntime/server": "^0.0.4"
+    "@skipruntime/server": "^0.0.6"
   },
   "devDependencies": {
     "@skiplabs/eslint-config": "^0.0.1",

but there is now an error at runtime:

$ docker compose up
...
reactive_cache-1  | node:internal/modules/esm/resolve:857
reactive_cache-1  |   throw new ERR_MODULE_NOT_FOUND(packageName, fileURLToPath(base), null);
reactive_cache-1  |         ^
reactive_cache-1  | 
reactive_cache-1  | Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'eventsource' imported from /app/node_modules/@skipruntime/core/dist/remote.js
reactive_cache-1  |     at packageResolve (node:internal/modules/esm/resolve:857:9)
reactive_cache-1  |     at moduleResolve (node:internal/modules/esm/resolve:926:18)
reactive_cache-1  |     at defaultResolve (node:internal/modules/esm/resolve:1056:11)
reactive_cache-1  |     at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:654:12)
reactive_cache-1  |     at #cachedDefaultResolve (node:internal/modules/esm/loader:603:25)
reactive_cache-1  |     at ModuleLoader.resolve (node:internal/modules/esm/loader:586:38)
reactive_cache-1  |     at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:242:38)
reactive_cache-1  |     at ModuleJob._link (node:internal/modules/esm/module_job:135:49) {
reactive_cache-1  |   code: 'ERR_MODULE_NOT_FOUND'
reactive_cache-1  | }
reactive_cache-1  | 
reactive_cache-1  | Node.js v22.12.0
reactive_cache-1 exited with code 1

[beauby]

The published version of @skipruntime/core seems to be missing a dependency on eventsource (which is now correctly stated in @skipruntime/helpers post 0c43e58).

[dyc3]

After pulling the latest changes, I'm still having trouble running this example.

The reactive_cache service doesn't start. Logs:

reactive_cache-1  |
reactive_cache-1  | > reactive-hackernews@1.0.0 start
reactive_cache-1  | > node server.js
reactive_cache-1  |
web-1             | WSGI app 0 (mountpoint='') ready in 0 seconds on interpreter 0x55e33f4f9ae0 pid: 1 (default app)
web-1             | *** uWSGI is running in multiple interpreter mode ***
web-1             | spawned uWSGI worker 1 (pid: 1, cores: 2)
web-1             | spawned uWSGI worker 2 (pid: 7, cores: 2)
web-1             | spawned uWSGI worker 3 (pid: 8, cores: 2)
web-1             | spawned uWSGI worker 4 (pid: 11, cores: 2)
reactive_cache-1  | Warning: The native version cannot be used on your system. The WASM version will be used.
reactive_cache-1  | node:internal/process/promises:394
reactive_cache-1  |     triggerUncaughtException(err, true /* fromPromise */);
reactive_cache-1  |     ^
reactive_cache-1  |
reactive_cache-1  | Error
reactive_cache-1  |     at EagerCollectionImpl.getUnique (file:///app/node_modules/@skipruntime/core/dist/index.js:97:19)
reactive_cache-1  |     at PostsMapper.mapEntry (file:///app/dist/hackernews.service.js:26:35)
reactive_cache-1  |     at ToBinding.SkipRuntime_Mapper__mapEntry (file:///app/node_modules/@skipruntime/core/dist/index.js:468:31)
reactive_cache-1  |     at LinksImpl.mapEntryOfMapper (file:///app/node_modules/@skipruntime/wasm/dist/src/internals/skipruntime_module.js:172:37)
reactive_cache-1  |     at libskip-runtime-ts-41aa2318dd3ebcd7.so.sk.SkipRuntime_ExternMapper__mapEntry (wasm://wasm/libskip-runtime-ts-41aa2318dd3ebcd7.so-0072d562:wasm-function[1894]:0x4b3b2)
reactive_cache-1  |     at libskip-runtime-ts-41aa2318dd3ebcd7.so.sk.SkipRuntime_Collection__map___Closure1__call__Closure0__call (wasm://wasm/libskip-runtime-ts-41aa2318dd3ebcd7.so-0072d562:wasm-function[2389]:0x61ff3)
reactive_cache-1  |     at libskip-runtime-ts-41aa2318dd3ebcd7.so.sk.vtry__Closure0__call.7 (wasm://wasm/libskip-runtime-ts-41aa2318dd3ebcd7.so-0072d562:wasm-function[2276]:0x5e15b)
reactive_cache-1  |     at libskip-runtime-ts-41aa2318dd3ebcd7.so.SKIP_call0 (wasm://wasm/libskip-runtime-ts-41aa2318dd3ebcd7.so-0072d562:wasm-function[3066]:0x8a128)
reactive_cache-1  |     at Utils.call (file:///app/node_modules/@skip-wasm/std/dist/sk_types.js:285:33)
reactive_cache-1  |     at Utils.etry [as SKIP_etry] (file:///app/node_modules/@skip-wasm/std/dist/sk_types.js:303:29)
reactive_cache-1  |
reactive_cache-1  | Node.js v22.12.0
reactive_cache-1 exited with code 1

[jberdine]

data point: I just tried and so far can't repro

[safareli]

I just pulled this repo and tried to run example using:

docker compose build
docker compose up

as specified in readme

and i see this errors in logs of the getting the reactive-hackernews :

2025-01-17 19:59:30 
2025-01-17 19:59:30 > reactive-hackernews@1.0.0 start
2025-01-17 19:59:30 > node server.js
2025-01-17 19:59:30 
2025-01-17 20:00:59 
2025-01-17 20:00:59 > reactive-hackernews@1.0.0 start
2025-01-17 20:00:59 > node server.js
2025-01-17 20:00:59 
2025-01-17 19:59:30 node:internal/modules/esm/resolve:857
2025-01-17 19:59:30   throw new ERR_MODULE_NOT_FOUND(packageName, fileURLToPath(base), null);
2025-01-17 19:59:30         ^
2025-01-17 19:59:30 
2025-01-17 19:59:30 Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'skip-wasm' imported from /app/node_modules/@skipruntime/server/dist/server.js
2025-01-17 19:59:30     at packageResolve (node:internal/modules/esm/resolve:857:9)
2025-01-17 19:59:30     at moduleResolve (node:internal/modules/esm/resolve:926:18)
2025-01-17 19:59:30     at defaultResolve (node:internal/modules/esm/resolve:1056:11)
2025-01-17 19:59:30     at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:654:12)
2025-01-17 19:59:30     at #cachedDefaultResolve (node:internal/modules/esm/loader:603:25)
2025-01-17 19:59:30     at ModuleLoader.resolve (node:internal/modules/esm/loader:586:38)
2025-01-17 19:59:30     at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:242:38)
2025-01-17 19:59:30     at ModuleJob._link (node:internal/modules/esm/module_job:135:49) {
2025-01-17 19:59:30   code: 'ERR_MODULE_NOT_FOUND'
2025-01-17 19:59:30 }
2025-01-17 19:59:30 
2025-01-17 19:59:30 Node.js v22.12.0
2025-01-17 20:00:59 node:internal/modules/esm/resolve:857
2025-01-17 20:00:59   throw new ERR_MODULE_NOT_FOUND(packageName, fileURLToPath(base), null);
2025-01-17 20:00:59         ^
2025-01-17 20:00:59 
2025-01-17 20:00:59 Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'skip-wasm' imported from /app/node_modules/@skipruntime/server/dist/server.js
2025-01-17 20:00:59     at packageResolve (node:internal/modules/esm/resolve:857:9)
2025-01-17 20:00:59     at moduleResolve (node:internal/modules/esm/resolve:926:18)
2025-01-17 20:00:59     at defaultResolve (node:internal/modules/esm/resolve:1056:11)
2025-01-17 20:00:59     at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:654:12)
2025-01-17 20:00:59     at #cachedDefaultResolve (node:internal/modules/esm/loader:603:25)
2025-01-17 20:00:59     at ModuleLoader.resolve (node:internal/modules/esm/loader:586:38)
2025-01-17 20:00:59     at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:242:38)
2025-01-17 20:00:59     at ModuleJob._link (node:internal/modules/esm/module_job:135:49) {
2025-01-17 20:00:59   code: 'ERR_MODULE_NOT_FOUND'
2025-01-17 20:00:59 }
2025-01-17 20:00:59 
2025-01-17 20:00:59 Node.js v22.12.0

[jberdine]

This issue may be due to package version mismatches since we currently have 0.m.p versions. #667 might help as it nails the versions down exactly.