Repository navigation
Conversation
@next/font crashes while collecting page data on Next 15.1. Use next/font/google with the latin subset previously set in fontLoaders, drop the unused package, and import tinykeys 3 as a named export. Co-authored-by: Ding Yi <dingyimac@gmail.com>
@calcom/embed-react 1.5.1 reads React 18 internals at import time, so the homepage fails page-data collection under React 19. The embed was already initialized inside useEffect. Co-authored-by: Ding Yi <dingyimac@gmail.com>
Review or Edit in CodeSandboxOpen the branch in Web Editor • VS Code • Insiders |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
You have reached your Code Terrier usage limits for code reviews. You can see your limits in the dashboard. |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
PR Summary
|
This branch had an error being deployed
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
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.
Summary
Production
pnpm run buildon Next 15.1 dies while collecting page data.pages/_app.tsximportsAlbert_Sansfrom@next/font/google, andcomponents/CommandMenu/index.tsxdefault-importstinykeys3.0.0, which only has a named export. This is the failure on deploymentdpl_HseVxHXXzrxquFzeGnAYaWHox7QE(commit7e17620). Canonical /og:urlbehavior from #398 is unchanged.next/font/googleforAlbert_Sansand forUnboundedincomponents/PageTitle/index.tsx(the other@next/fontimport). Passsubsets: ['latin'], which is whatexperimental.fontLoadersdeclared. Next 15 already ignores that key.@next/fontdependency and the unusedfontLoadersconfig.import { tinykeys } from "tinykeys".@calcom/embed-reactinside the existinguseEffect. v1.5.1 reads React 18 internals at import time and throws under React 19 (ReactCurrentOwner/ReactCurrentDispatcher). That crash was hidden behind the font error and stops page-data collection for/. No dependency upgrade.Verification
pnpm run buildon this branch:@next/font/google failed to run or is incorrectly configurederror and thetinykeysdefault-export warning are gone././gearwith NotionAPIResponseError: Authorization header must use the format "Bearer <token>"because this environment has noNOTION_API_KEY. The Vercel project already definesNOTION_API_KEY, the Notion database ids, and the Raindrop/Spotify variables for production, so that failure should not reproduce on Vercel.This PR was generated automatically by Cursor.