4 Answers
- Newest
- Most votes
- Most comments
0
cache size issue. see here for workaround:
answered 5 years ago
0
You could solve it by removing any override package version in Amplify build settings.
You might add npm i -g @aws-amplify/cli as a preBuild command, which forces a reset in the cache.
version: 1
backend:
phases:
preBuild:
commands:
- npm i -g @aws-amplify/cli
build:
commands:
- '# Execute Amplify CLI with the helper script'
- amplifyPush --simple
frontend:
phases:
preBuild:
commands:
- npm ci
build:
commands:
- npm run build
artifacts:
baseDirectory: .next
files:
- '**/*'
cache:
paths:
- node_modules/**/*
answered 9 months ago
Relevant content
- asked 2 months ago
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 6 months ago