We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
paraglide-next currently doesn't work with static export.
paraglide-next
Blockers:
middleware
rewrites
headers
[locale]
Add a way to bypass the blockers if static export is desired
use
<link rel="alternate">
Link
Static export is the exceptional case, but people expect support for it.
The text was updated successfully, but these errors were encountered:
LorisSigrist
No branches or pull requests
Context
paraglide-next
currently doesn't work with static export.Blockers:
middleware
for language detection &rewrites
-> Not supportedheaders
to manage language state on the server -> Not supported[locale]
parameter, so pages can't be rendered multiple times (very silly limitation from NextJS)Proposal
Add a way to bypass the blockers if static export is desired
[locale]
parameter for rendering multiple pages[locale]
parameter for server-side language state. We can use react'suse
hook to scope the state to the request -> No crosstalk<link rel="alternate">
links instead of using theLink
headerStatic export is the exceptional case, but people expect support for it.
The text was updated successfully, but these errors were encountered: