Update Documentation

[samcx]

Issue

We've been getting cases where users are not able to build their Next.js page when using this package (working locally but not on Vercel).

It turns out people are using getServerSideProps for their page, which I believe is not supposed to work since the documentation also states getInitialProps does not work (both methods are almost identical).

When accessing the getServerSideProps page →

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/isaachinman/next-i18next/FRfzKDzKwgZpRzGsFeBxaGWkHSSM
✅ Preview: https://next-i18next-git-fork-vercel-support-update-docs-isaachinman.vercel.app

[isaachinman]

The getServerSideProps data fetching method absolutely is supported. What you are encountering is a drawback of Vercel's serverless architecture, which has been raised and answered countless times in issues on this repo. You will need to use path.resolve to instruct the Vercel platform to keep those localisation files in the serverless output.

Feel free to search existing issues, eg: #1141

[samcx]

@isaachinman Thanks for the clarification. Would it be possible to add documentation for getServerSideProps?

[isaachinman]

Hi @samsisle – this issue is not specific to getServerSideProps, it affects all data-fetching methods. Sure, we could add documentation about Vercel-specific requirements in the notes section.