updated video.. super cool. but i do a test on production, its give the error [Error]: Expected signal to be an instanceof AbortSignal. Even i try on npm run start after build, got the same error. Do you have any solution on it?
Very good catch, I did also get this when I ran it in a "production" docker container. The fix is to add this line into your next.config file: experimental: { serverMinification: false, }, For some reason, that serverMinification is an experimental feature and turned on by default (which is...odd). Here is where I found the solution after some searching: github.com/vercel/next.js/issues/55682
Even if the file is too large it will work fine on your localhost but in production it will definitely break. I got this error on my production build and it’s still not fixed. Still trying to figure it out with api routes do you have any idea?
I don't fully understand your point. My application is published on Vercel, and I solely utilize GCP Storage for storage purposes. Thus, this setup can be implemented even if the application is not running on a laptops.
updated video.. super cool. but i do a test on production, its give the error [Error]: Expected signal to be an instanceof AbortSignal. Even i try on npm run start after build, got the same error. Do you have any solution on it?
Very good catch, I did also get this when I ran it in a "production" docker container.
The fix is to add this line into your next.config file:
experimental: {
serverMinification: false,
},
For some reason, that serverMinification is an experimental feature and turned on by default (which is...odd).
Here is where I found the solution after some searching:
github.com/vercel/next.js/issues/55682
Thanks.. its work.. waiting for next video..
you greatly helped me with my project too. Thank you so much for spending the time to make this content. I owe you.
Thank you so much! Helped me a lot. Your videos are amazing
Happy to help!
Thanks... keep uploading new videos
nice explanation!
Thanks!
Even if the file is too large it will work fine on your localhost but in production it will definitely break. I got this error on my production build and it’s still not fixed. Still trying to figure it out with api routes do you have any idea?
You probably want to look into using Put SignedUrls. I’ve used those for large file uploads before and they work well
Nice please do next js file upload with aws s3
worked for me!
yeah that's a good example you showed us how to do it when we are using the app on our laptop. Because who needs to deploy any appilication right?
What else would you like to know for it to be deployed?
I don't fully understand your point. My application is published on Vercel, and I solely utilize GCP Storage for storage purposes. Thus, this setup can be implemented even if the application is not running on a laptops.
for the great value you are getting why be so rude ?
@@C3drix how about keys? locally you're logged in to your google account how Vercel knows about it?