Use pnpm --recursive processing scheme for install, build and publish phases

scripts/bash/npm-helpers/npm_build_package.sh

@@ -15,7 +15,7 @@ pushd "${SOURCE_DIR}" # move to the project directory (where package.json file i
 
 "${SCRIPTPATH}/npm_generate_version.sh" "${SOURCE_DIR}" "${REGISTRY_URL}" "${SCOPE}" "${PROJECT_NAME}" "${COMMIT_REF_PROTECTED}" "${COMMIT_TAG}"
 
-npm run build
+pnpm --recursive --workspace-concurrency=1 run build
 
 "${SCRIPTPATH}/npm_pack_package.sh" "${SOURCE_DIR}" "${REGISTRY_URL}" "${SCOPE}" "${PROJECT_NAME}" "${OUTPUT_DIR}" "${COMMIT_REF_PROTECTED}" "${COMMIT_TAG}"
 

scripts/bash/npm-helpers/npm_publish.sh

@@ -40,7 +40,7 @@ else
   set -e
   echo "Publishing ${NAME}@${VERSION} to tag ${PACKAGE_DIST_TAG}"
   # We are going to repack the tarball as there are registry-dependent data in each job for package.json
-  pnpm publish --no-git-checks --access=public --tag "${PACKAGE_DIST_TAG}"
+  pnpm --recursive publish --no-git-checks --access=public --tag "${PACKAGE_DIST_TAG}"
 fi
 
 popd

templates/npm_projects.gitlab-ci.yml

@@ -28,7 +28,7 @@ variables:
 
   before_script:
     - !reference [.node_based_job_base, before_script]
-    - pnpm install --frozen-lockfile  # install all required dependencies
+    - pnpm --recursive install --frozen-lockfile  # install all required dependencies
 
 .filter_out_swagger_json:
   extends: .node_based_job_base