Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Custom server warning in README #325

Closed
elbotho opened this issue May 29, 2019 · 2 comments
Closed

Custom server warning in README #325

elbotho opened this issue May 29, 2019 · 2 comments

Comments

@elbotho
Copy link
Contributor

elbotho commented May 29, 2019 •
edited

I think the readme should include a clear warning, that next-i18next requires a custom server and can therefore not be used with next export or serverless (e.g. now V2).

I guess it's implicitly stated, but it took me quite a long time to piece it together.
This might affect many next users.

Relevant Issues
#25 and #10
@isaachinman
Copy link
Contributor

It can be used with next export and there's already a notice about this in the README.

The installation instructions clearly state the process involving a custom server and in no way suggest that these steps are optional. What would be a helpful way to communicate this further?

We are tracking serverless support with #274.

@elbotho
Copy link
Contributor Author

elbotho commented May 29, 2019

It sure had to do with my steep next-learning curve. I didn't realise that custom servers and now v2 don't go well together at first.
Maybe a note with link to the issue (#274) would be helpful.

@elbotho elbotho mentioned this issue May 29, 2019
Merged
isaachinman pushed a commit that referenced this issue May 30, 2019
@elbotho @isaachinman
docs: Add note to README about serverless (#326)
4f8cf80 
* Update README: Note about serverless deployment

as proposed in #325.

* real grammar
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@elbotho @isaachinman