4 Risposte
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
0
cache size issue. see here for workaround:
con risposta 5 anni fa
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/**/*
con risposta 9 mesi fa
Contenuto pertinente
- AWS UFFICIALEAggiornata 2 anni fa