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.

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

fix: Allow to import next-intl/server into Client Components (however not call any functions). This allows for easier testing of page components with multiple exports. #683

Merged
merged 1 commit into from
Dec 1, 2023

Conversation

amannn
Copy link
Owner

@amannn amannn commented Dec 1, 2023

Fixes #681

…er not call any functions). This allows for easier testing of page components with multiple exports.
Copy link

vercel bot commented Dec 1, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
next-intl-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Dec 1, 2023 11:59am
next-intl-example-app-router ✅ Ready (Inspect) Visit Preview 💬 Add feedback Dec 1, 2023 11:59am

@amannn amannn marked this pull request as ready for review December 1, 2023 12:04
@amannn amannn merged commit 5ca4075 into main Dec 1, 2023
5 checks passed
@amannn amannn deleted the fix/681-allow-to-import-server-in-client-env branch December 1, 2023 12:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Imports from next-intl/server break Jest due to export syntax
1 participant