Unable to get typescript handlers automatically working after cds build.

[dvvelzen]

Hi,

When I run a new sample CAP project with TS support locally with cds watch everything runs fine.

However after running the cds build --production, part of the MTA Builder, the Typescript files get moved into the wrong directory.

The copied .ts files from the nodejs build are in the correct place, they aren't actually there after the build.
However the compiled files for typescript moves them to the gen/srv instead of the gen/srv/srv

Eventually this results into this structure;

So when the server starts it doesn't find the compiled handler files and start with a default implementation.

I'm now using the tsconfig.cdsbuild.json configuration with an updated outdir value;

{
  "extends": "./tsconfig.json",
  "compilerOptions": {
    "outDir": "./gen/srv/srv"
  },
  "exclude": ["app", "gen"]
}

Why is this needed?

[daogrady]

Hi @dvvelzen ,

Why is this needed?

Shouldn't be. Can you please provide a reproduction sample? Thanks!
(I saw that you referred to the sample project, but I'd like to make sure I include the correct facets, configs, etc., as I am seeing the following output for a barebones sample project:

which appears to be in order.)

Best,
Daniel

[dvvelzen]

Hi @daogrady,

You are right in a new empty project with cds init <name> --add typescript it works fine.

The culprit is in the tsconfig.json include:

{
  ...
  ,"include": ["srv/**/*.ts"]
}

This was added to actually ignore other typescript files in the project setup, for example the utility scripts in the project root and the unit tests in test/.

I recon this is inferring the rootDir to switch from . to srv/. Which is by default not part of the tsconfig.json file in the barebone project.

After adding rootDir to the tsconfig.json it works fine;

{
  "compilerOptions": {
    ...
    ,"rootDir": "."
    ...
  }
}

Sorry for the inconvenience.
Dennis

[daogrady]

Hi @dvvelzen ,

no worries, glad you could find a solution!

Best,
Daniel