npmExecuteScripts fails with ENOWORKSPACES

[navinkrishnan]

Hi,
In the project package.json, I have configured workspaces

 "workspaces": [
    "app/*"
  ]

In the pipeline config, I have the following for npmExecuteScripts

  npmExecuteScripts: 
    install: true
    publish: false
    runScripts: 
      - "production-build"

This results in the error:

info  npmExecuteScripts - Discovered package.json file package.json
12:14:56  info  npmExecuteScripts - running command: npm config get registry
12:14:56  error npmExecuteScripts - npm ERR! code ENOWORKSPACES
12:14:56  error npmExecuteScripts - npm ERR! This command does not support workspaces.
12:14:56  info  npmExecuteScripts - 
12:14:56  error npmExecuteScripts - npm ERR! A complete log of this run can be found in: /root/.npm/_logs/2024-05-15T06_44_55_325Z-debug-0.log

[anilkeshav27]

the npm build does not support workspaces currently

[navinkrishnan]

Hi @anilkeshav27 , how do we handle project with workspaces. The above error is not for the script I wanted to run, but rather npmExecuteScripts automatically runs the command npm config get registry and it fails.

[js1972]

This is bad news. The best practice that is developing for CAP/UI5 apps is to use npm workspaces as it allows the CAP tooling to work alongside the UI5 tooling. And now our CICD service can't handle it. Is there a workaround to this?

[anilkeshav27]

This is bad news. The best practice that is developing for CAP/UI5 apps is to use npm workspaces as it allows the CAP tooling to work alongside the UI5 tooling. And now our CICD service can't handle it. Is there a workaround to this?

could you point me to some documentation about the CAP apps to use npm workspaces, since we lack this functionality some pointers about best practises is a good place to try a bring in workspaces support in piper

[anilkeshav27]

Hi @anilkeshav27 , how do we handle project with workspaces. The above error is not for the script I wanted to run, but rather npmExecuteScripts automatically runs the command npm config get registry and it fails.

npm commands to set/get registry is baked into the npm steps themselves to fetch from cached npm registry and not npmjs.
my guess is that when we try to run the first npm command it fails when it encounters WORKSPACES in the package.json

[github-actions]

Thank you for your contribution! This issue is stale because it has been open 60 days with no activity. In order to keep it open, please remove stale label or add a comment within the next 10 days. If you need a Piper team member to remove the stale label make sure to add @SAP/jenkins-library-team to your comment.

[github-actions]

Issue got stale and no further activity happened. It has automatically been closed. Please re-open in case you still consider it relevant.