fix: supprimer async inutile sur WhyChallenge#516
Merged
cyrilledaily merged 2 commits intomainfrom Feb 20, 2026
Merged
Conversation
…nt Component WhyChallenge n'effectue aucune opération asynchrone. Le mot-clé `async` provoquait deux erreurs Next.js quand le composant était rendu depuis interpeller/page.tsx (marqué 'use client') : - "async Client Component" non supporté - "suspended by an uncached promise" Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Contributor
|
Preview is deploying...| ℹ️ Name | 🔗 Infos & links |
|---|---|
| 🌱 Deploying commit | ec6fe1f |
| 👁️ Preview | Generating preview app... |
cyrilledaily
approved these changes
Feb 20, 2026
Collaborator
cyrilledaily
left a comment
cyrilledaily
left a comment
There was a problem hiding this comment.
LGTM — fix correct et nécessaire.
WhyChallenge n'a aucune opération asynchrone, le async était superflu et causait des erreurs Next.js 15 quand le composant est importé depuis un client component (ce qui est le cas sur /interpeller).
Fix minimal, une seule ligne, aucun risque de régression.
✅ Approuvé
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problème
La page
/interpeller('use client') importeWhyChallenge, déclaréasync function. Cela provoque deux erreurs Next.js 15 :async Client Component— React/Next.js n'autoriseasyncque sur les Server Componentssuspended by an uncached promise— React tente d'exécuter la promesse côté client sans cacheCause
WhyChallengen'effectue aucune opération asynchrone. Leasyncétait superflu et a été ajouté par erreur.Fix
Suppression du mot-clé
asyncsurWhyChallenge. Le composant reste fonctionellement identique.Test plan
/interpelleren local → plus d'erreurs consoleWhyChallenges'affiche correctement sur la pageWhyChallenges'affiche correctement sur la page d'accueil (/)🤖 Generated with Claude Code