Environment info
firebase-tools: 13.1.0
Platform: macOS
Test case
Create a new next.js project and then attempt to deploy it to Firebase, the functions folder will be huge like 100MB or upto 300MB.
Steps to reproduce
Create a new next.js project and then attempt to deploy it to Firebase, the functions folder will be huge like 100MB or upto 300MB.
Expected behavior
The .next/cache folder should be ignored by Firebase Functions.
Actual behavior
The .next/cache folder is being copied over to .firebase/app-name/functions/.next/cache
Environment info
firebase-tools: 13.1.0
Platform: macOS
Test case
Create a new next.js project and then attempt to deploy it to Firebase, the functions folder will be huge like 100MB or upto 300MB.
Steps to reproduce
Create a new next.js project and then attempt to deploy it to Firebase, the functions folder will be huge like 100MB or upto 300MB.
Expected behavior
The
.next/cachefolder should be ignored by Firebase Functions.Actual behavior
The
.next/cachefolder is being copied over to.firebase/app-name/functions/.next/cache