CAP-Apps crashes after deploying when trying to start

[haykma]

Hi Community,

i have developed a cap-application which i already could deploy in the past. Now, after developing a while and testing in hybrid mode (using destination), i tried to build and deploy the actual state.
After deploying when the deployer tries to start the cap-app (approuter + service) i get the error "cds: not found".
Does anyone have an idea where to look and how to solve this error?

As an attachment i have added a screenshot from log of deployment to btp.

kind regards
Matthias

[chgeo]

Please check your `package.json` (at root level or in `srv`) to have `@sap/cds` as a dependency. This module has the `cds` executable that is missing here.

[haykma]

Hi christian.georgi

thanks for your answer.
I have already an entry for "@sap/cds" in package.json in section "dependencies" of root.

See attached screenshot of the dependencies-section of package.json

crash-cdsnotfound2.jpg

regards
Matthias

[chgeo]

Dependency list looks good. Not sure what caused the issue then.

Check after `cds build` that gen/srv/package.json is correct

If not, check that there is no duplicate of package.json in your code tree

Check the npm start script

Try locally by using `npm start` after npm install'ing all modules again

Provide the full error log.

[haykma]

Hi christian.georgi ,

package.json is present in the right place after building (its in gen/srv/package.json). and has the same values in dependenies-section.
I' will try to get more details

kind regards
Matthias

[haykma · Accepted solution]

I don't really now what happend and why i had this problems.
I tried Windows Linux Shell (WLS) for building and deploying. Created a new package-lock.json.
And after doing this it suddenly worked...

Thanx to christian.georgi for caring.

kind regards
Matthias

[karstenvoigt · Accepted solution]

Thanks for your answer; I had a similar issue and checking (updating) the package-lock.json did solve it.