-
-
Notifications
You must be signed in to change notification settings - Fork 764
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error with getServerSideProps and next-i18next@^8.0.0-beta.2 #919
Comments
This is precisely the problem. |
Do you have a reproducible repo? |
Repo: https://github.com/Achaak/next-i18next-issue |
I am encountering the same problem using Incremental Static Regeneration and deploying on Vercel. Version 8.0.0-beta.4 |
This looks to me like a transient filesystem issue which is probably pretty specific to Vercel. @Achaak or @destruc7i0n can you open a support ticket with Vercel and ask them why these files are available during SSG but not during SSR? |
Not sure how you phrased the support ticket, but you'll need to make it clear this is a filesystem issue, and is not specifically related to third-party packages. |
Yes, maybe we could try again but I've said exactly this:
|
I was able to resolve this by placing the following call above the usage of
They appear to be using vercel/nft to see which files to include in the serverless runtime. |
Yep, that makes sense, and that is why |
I have test but with next-i18next-config.js or path.resolve (in getServerSideProps) and not work for me. Version: next-i18next@^8.0.0-beta.4 Check my repo : |
Did anybody got the solution? Facing the same when using SSR, works well with SSG |
module.exports = { |
Describe the bug
Error 502 in vercel, when using getServerSideProps with next-i18next@^8.0.0-beta.2
Occurs in next-i18next version
next-i18next@^8.0.0-beta.2
Steps to reproduce
Create dynamic page with next-i18next and getServerSideProps
Screenshots
OS
The text was updated successfully, but these errors were encountered: