Skip to content

Commit ebd0cd3

Browse files
authored
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*
1 parent 457e02a commit ebd0cd3

File tree

1 file changed

+0
-3
lines changed

1 file changed

+0
-3
lines changed

buildspec.yaml

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -10,9 +10,6 @@ phases:
1010
# this also takes care of launching the docker daemon.
1111
- /root/ecr-proxy/start.sh
1212

13-
# CodeBuild always runs as root, allow npm to operate as such
14-
- npm config set unsafe-perm true
15-
1613
# Install yarn if it wasn't already present in the image
1714
- yarn --version || npm -g install yarn
1815

0 commit comments

Comments
 (0)