SAP CAP deployment fails in SAP BAS package not found

[VoJu]

Hello together,

I have created with yo a basic CAP project with sample files in Business Application Studio.

Creating new cap project in ./test
Adding feature 'nodejs'... 
Adding feature 'mta'... 
Adding feature 'samples'... 
Done adding features
Continue with 'cd test'

I executed commands "npm install" and "cds watch". The CAP is working.

After right click on mta.yaml file and executing "MTA Build Project" the following error appears:

INFO executing the "npx -p @sap/cds-dk cds build --production" command...
npm WARN exec The following package was not found and will be installed: @sap/cds-dk
.npm notice Beginning October 4, 2021, all connections to the npm registry - including for package installation - must use TLS 1.2 or higher. You are currently using plaintext http to connect. Please visit the GitHub blog for more information: https://github.blog/2021-08-23-npm-registry-deprecating-tls-1-0-tls-1-1/
npm notice Beginning October 4, 2021, all connections to the npm registry - including for package installation - must use TLS 1.2 or higher. You are currently using plaintext http to connect. Please visit the GitHub blog for more information: https://github.blog/2021-08-23-npm-registry-deprecating-tls-1-0-tls-1-1/
......npm ERR! code E404
npm ERR! 404 Not Found - GET http://nginx-redirector.repo-cache.svc.cluster.local/yocto-queue/-/yocto-queue-0.1.0.tgz
npm ERR! 404 
npm ERR! 404  'https://registry.npmjs.org/yocto-queue/-/yocto-queue-0.1.0.tgz' is not in this registry.
npm ERR! 404 This package name is not valid, because 
npm ERR! 404  1. name can only contain URL-friendly characters
npm ERR! 404 
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

Has anyone an idea how to resolve the issue?

Thanks a lot and best regards,

Julian

[1joandre]

Hello Julian

I have the same problem.... An application that was building correctly and now....

npm notice Beginning October 4, 2021, all connections to the npm registry - including for package installation - must use TLS 1.2 or higher. You are currently using plaintext http to connect. Please visit the GitHub blog for more information: https://github.blog/2021-08-23-npm-registry-deprecating-tls-1-0-tls-1-1/
.....npm ERR! code E404
npm ERR! 404 Not Found - GET http://nginx-redirector.repo-cache.svc.cluster.local/yocto-queue/-/yocto-queue-0.1.0.tgz
npm ERR! 404 
npm ERR! 404  'https://registry.npmjs.org/yocto-queue/-/yocto-queue-0.1.0.tgz' is not in this registry.
npm ERR! 404 This package name is not valid, because 
npm ERR! 404  1. name can only contain URL-friendly characters
npm ERR! 404 
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

Thanks and regards

Ignacio

[VoJu]

Hi Ignacio,

ok, than we have the same behavior yesterday my application was also building correctly.

best regards,

Julian

[patricebender]

A colleague of mine was able to fix this with the following workaround

echo registry=https://registry.npmjs.org/ > .npmrc
echo registry=https://registry.npmjs.org/ > app/.npmrc
echo registry=https://registry.npmjs.org/ > db/.npmrc

[1joandre]

Hello Patrice

Thanks very much!!!

I was able to fix it with this solution

Regards

Ignacio

[VoJu]

Hi Patrice,

indeed this is a workaround and working for me at the moment.

Best regards,

Julian

[chgeo]

Same as https://answers.sap.com/questions/13544661/

[Nachshon]

Can you share which region are you using?

[VoJu]

EU, but also in Trail Version I had the issue.

[liat_b · Accepted solution]

Hi,

We will look into this issue. In the meanwhile the workaround mentioned in the comments would work, since it goes around the cache that seems to be the cause for this issue:

echo registry=https://registry.npmjs.org/ > .npmrc

[ankit_pundhir · Accepted solution]

Thanks Liat, you saved my day. 🙂

[Girish_Kumar_Gu · Accepted solution]

I had the same issue, but this workaround works great!!