Building Fullstack Application with ts-node - node.js

Question

I am currently having a problem in the build process of my typescript application.
Currently this application is an api using the express framework.
It is run in development mode via ts-node and compiled with tsc:
npm run dev
node --inspect=0.0.0.0:9229 -r ts-node/register -r tsconfig-paths/register ./src/index.ts
npm run build
tsc -p tsconfig.build.json && tsc-alias -p tsconfig.build.json --silent
I now want to integrate a react ssr client to this application server.
So far no problem my first solution was to make a monorepo style architecture with different packages.json and build my react application independently then give the generated statics files to express.
The problem appeared when integrating react-router into my architecture.
Indeed I can no longer just serve static files I need to serve a static router from react router.
I'm not going to dwell on why I need my application to be isomorphic (I leave you this more than complete comment to answer the question: https://stackoverflow.com/a/36623117/11312725) but when I 'integrate my react to my server the build no longer works.
Whether it's ts-node or tsc, the build is down..
tsconfig.json
{
"compilerOptions": {
// Project options
"allowJs": true, // Allow JavaScript files to be imported inside your project, instead of just .ts and .tsx files
"declaration": false, // Generate .d.ts files for every TypeScript or JavaScript file inside your project
"lib": ["es2019", "es2020", "es2021", "esnext"], // Specifies which default set of type definitions to use ("DOM", "ES6", etc)
"module": "commonjs", // Sets the module system for the program. "CommonJS" for node projects.
"noEmit": false, // Do not emit compiler output files like JavaScript source code, source-maps or declarations.
"outDir": "./dist", // .js (as well as .d.ts, .js.map, etc.) files will be emitted into this directory
"rootDir": "./", // The longest common path of all non-declaration input files
"sourceMap": true, // Enables the generation of sourcemap files
"target": "es2019", // Target environment
// Module resolution
"baseUrl": "./", // Sets a base directory to resolve non-absolute module names
"esModuleInterop": true, // fixes some issues TS originally had with the ES6 spec where TypeScript treats CommonJS/AMD/UMD modules similar to ES6 module
"moduleResolution": "node", // Pretty much always node for modern JS. Other option is "classic"
"paths": {
"#application/*": ["src/application/*"],
"#domain/*": ["src/domain/*"],
"#infrastructure/*": ["src/infrastructure/*"],
"#presentation/*": ["src/presentation/*"],
"#test/*": ["test/*"],
"#/*": ["src/*"]
}, // A series of entries which re-map imports to lookup locations relative to the baseUrl
"typeRoots": ["../node_modules/#types", "node_modules/#types", "src/types"],
// Advanced
"forceConsistentCasingInFileNames": true, // TypeScript will issue an error if a program tries to include a file by a casing different from the casing on disk
"listEmittedFiles": false, // Print names of generated files part of the compilation
"listFiles": false, // Print names of files part of the compilation
"resolveJsonModule": true, // Allows importing modules with a ‘.json’ extension, which is a common practice in node projects
"skipLibCheck": true, // Skip type checking of declaration files
"traceResolution": false, // Report module resolution log messages
// Experimental
"experimentalDecorators": true, // Enables experimental support for decorators
"emitDecoratorMetadata": true, // Enables experimental support for emitting type metadata for decorators which works with the module
// Strict checks
"strict": true, // Enable all strict type-checking options
// "allowUnreachableCode": false, // Pick up dead code paths
// "alwaysStrict": true, // Parse in strict mode and emit "use strict" for each source file
// "noImplicitAny": true, // Raise error on expressions and declarations with an implied 'any' type
// "noImplicitThis": true, // Raise error on 'this' expressions with an implied 'any' type
// "strictFunctionTypes": true, // Enable strict checking of function types
// "strictNullChecks": true, // Enable strict null checks
"strictPropertyInitialization": false, // Enable strict checking of property initialization in classes
// Linter Checks
"noFallthroughCasesInSwitch": true, // Report errors for fallthrough cases in switch statement
"noImplicitReturns": true, // Report error when not all code paths in function return a value
"noUnusedLocals": true, // Report errors on unused local variables
"noUnusedParameters": true, // Report errors on unused parameters
"pretty": true // Stylize errors and messages using color and context
},
"exclude": ["node_modules", "dist"], // Specifies an array of filenames or patterns that should be skipped when resolving include
"compileOnSave": false // Compile on save
}
tsconfig.build.json
{
"extends": "./tsconfig.json",
"compilerOptions": {
"sourceMap": false,
"inlineSourceMap": true,
"rootDir": "./src"
},
"include": ["src/**/*"],
"exclude": ["src/**/*.test.ts", "src/**/*.spec.ts", "test/**/*.test.ts", "test/**/*.spec.ts", "node_modules", "dist"]
}
I already tried to build my entire application with webpack but it is a non-sense because webpack is used for frontend app.