AWS Amplify Looks Simple, Until It Is Not

Short summary

AWS Amplify's built-in caching paradoxically slows builds—npm ci immediately deletes the restored node_modules folder, negating the 6-minute overhead. The 220MB artifact limit causes silent failures on larger Next.js projects; enable standalone output mode to reduce size. pnpm's symlinks break at runtime on Amplify; force hoisted mode or switch to npm.

• •Disable Amplify caching entirely—npm ci deletes restored node_modules immediately, making cache restoration slower than fresh installs
• •220MB artifact limit silently fails on Next.js SSR projects; use standalone output mode in next.config.js to reduce bundle size
• •pnpm symlinks cause runtime module-not-found errors on Amplify; force hoisted installation or use npm instead

Generated with AI, which can make mistakes.