Server example > Error: Debug Failure. False expression: Non-string value passed to ts.resolveTypeReferenceDirective

[jermay]

Summary

When attempting to run the sever example with yarn start a type error occurs

Steps to reproduce

1. Follow the instructions in the /examples/server readme to install and build the example, except need to add an empty yarn.lock file so the dependencies will install.
2. yarn start

Current behavior

The following error occurs:

$ yarn start
[INFO] 10:32:52 ts-node-dev ver. 1.1.8 (using ts-node ver. 9.1.1, typescript ver. 4.7.3)
Compilation error in C:\Users\Jeremy\Documents\Code\unstoppable\uauth\examples\server\src\index.ts
Error: Debug Failure. False expression: Non-string value passed to `ts.resolveTypeReferenceDirective`, likely by a wrapping package working with an outdated `resolveTypeReferenceDirectives` signature. This is probably not 
a problem in TS itself.
    at Object.<anonymous> (C:\Users\Jeremy\Documents\Code\unstoppable\uauth\examples\server\src\index.ts:1:7)
    at Module._compile (node:internal/modules/cjs/loader:1101:14)
    at Module._compile (C:\Users\Jeremy\Documents\Code\unstoppable\uauth\examples\server\node_modules\source-map-support\source-map-support.js:568:25)
    at Module.m._compile (C:\Users\Jeremy\AppData\Local\Temp\ts-node-dev-hook-48050745786656734.js:69:33)
    at Module._extensions..js (node:internal/modules/cjs/loader:1153:10)
    at require.extensions..jsx.require.extensions..js (C:\Users\Jeremy\AppData\Local\Temp\ts-node-dev-hook-48050745786656734.js:114:20)
    at require.extensions.<computed> (C:\Users\Jeremy\AppData\Local\Temp\ts-node-dev-hook-48050745786656734.js:71:20)
    at Object.nodeDevHook [as .ts] (C:\Users\Jeremy\Documents\Code\unstoppable\uauth\examples\server\node_modules\ts-node-dev\lib\hook.js:63:13)
    at Module.load (node:internal/modules/cjs/loader:981:32)
    at Function.Module._load (node:internal/modules/cjs/loader:822:12)
[ERROR] 10:32:52 Error: Debug Failure. False expression: Non-string value passed to `ts.resolveTypeReferenceDirective`, likely by a wrapping package working with an outdated `resolveTypeReferenceDirectives` signature. This is probably not a problem in TS itself.

Expected behavior

The express server is started

Solution

Update ts-node-dev dependency to version 2.0.0