From 5723410a50f041d0c87acca5d08f1c1465d7f1bc Mon Sep 17 00:00:00 2001 From: Momo Kornher Date: Mon, 20 Nov 2023 09:06:30 +0100 Subject: [PATCH] chore: pr-build failing with unsafe-perm is not a valid npm option We switched the images used to build PRs to `jsii/superchain:bullseye-slim-node18` which comes with Node.js 18 instead of Node.js 16. This Node.js upgrade also includes an upgraded version of npm, and in recent npm versions, the unsef-perm option is not required anymore. This change simply removes the now redundant command. --- buildspec-pr.yaml | 3 --- 1 file changed, 3 deletions(-) diff --git a/buildspec-pr.yaml b/buildspec-pr.yaml index 1168f54b338ae..852070e934e86 100644 --- a/buildspec-pr.yaml +++ b/buildspec-pr.yaml @@ -14,9 +14,6 @@ phases: # this also takes care of launching the docker daemon. - /root/ecr-proxy/start.sh - # CodeBuild always runs as root, allow npm to operate as such - - npm config set unsafe-perm true - # Install yarn if it wasn't already present in the image - yarn --version || npm -g install yarn