From 1cc484bf7de0dc2122e876bbf2d19c8939eb5f92 Mon Sep 17 00:00:00 2001 From: Momo Kornher Date: Mon, 20 Nov 2023 14:55:31 +0100 Subject: [PATCH] chore: build failing with unsafe-perm is not a valid npm option (#28069) We switched the images used to run our main build 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. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license* --- buildspec.yaml | 3 --- 1 file changed, 3 deletions(-) diff --git a/buildspec.yaml b/buildspec.yaml index 9efaf655e95c1..b54c07f3b99c1 100644 --- a/buildspec.yaml +++ b/buildspec.yaml @@ -10,9 +10,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