Skip to content

Commit 457e02a

Browse files
authoredNov 20, 2023
chore: pr-build failing with unsafe-perm is not a valid npm option (aws#28068)
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. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
1 parent c66e197 commit 457e02a

File tree

1 file changed

+0
-3
lines changed

1 file changed

+0
-3
lines changed
 

‎buildspec-pr.yaml

-3
Original file line numberDiff line numberDiff line change
@@ -14,9 +14,6 @@ phases:
1414
# this also takes care of launching the docker daemon.
1515
- /root/ecr-proxy/start.sh
1616

17-
# CodeBuild always runs as root, allow npm to operate as such
18-
- npm config set unsafe-perm true
19-
2017
# Install yarn if it wasn't already present in the image
2118
- yarn --version || npm -g install yarn
2219

0 commit comments

Comments
 (0)
Please sign in to comment.