Next15 (#279)

[dinmukhamedm]

• first upgrade to next 15

• fix posthog issue - question in https://posthog.com/docs/libraries/next-js

• update pnpm lock

• codemod for async params https://nextjs.org/docs/messages/sync-dynamic-apis#possible-ways-to-fix-it

• add a setting to remove Yjs dual import warning

• remove 'view'

• fix build, mostly by removing unused params in pages

• fix build again: downgrade react-day-picker

• pnpm update to fix some peerdeps

• some more updates to deps

• further pnpm update

• update react-day-picker with a few quick styling hacks

• fix build: react day picker v9

• restore deleted route, fix avatar on localhost

---

Important

Upgrade to Next.js 15 with async parameter handling, dependency updates, and build fixes.

• Upgrade:
  • Upgrade to Next.js 15.
  • Update pnpm lock file.
  • Downgrade react-day-picker to fix build issues.
• Code Changes:
  • Modify async parameter handling in multiple route.ts files to use props: { params: Promise<...> }.
  • Add setting to remove Yjs dual import warning in next.config.js.
  • Restore deleted route and fix avatar display on localhost.
• Dependencies:
  • Update various dependencies in package.json, including @aws-sdk/client-s3, @supabase/supabase-js, and react-day-picker.
  • Remove use-enter-submit.tsx hook.
• Miscellaneous:
  • Minor styling and component adjustments in pipeline-bottom-panel.tsx and calendar.tsx.
  • Fix typo in README.md.

^{This description was created by for 55767df. It will automatically update as commits are pushed.}

[ellipsis-dev]

👍 Looks good to me! Reviewed everything up to 55767df in 1 minute and 51 seconds

More details

• Looked at 2400 lines of code in 94 files
• Skipped 1 files when reviewing.
• Skipped posting 8 drafted comments based on config settings.

1. frontend/app/api/projects/[projectId]/traces/[traceId]/route.ts:8

• Draft comment:
  The use of Promise for params in the function signature is unnecessary. You can directly destructure params without wrapping it in a Promise. This pattern is repeated across multiple files.
• Reason this comment was not posted:
  Decided after close inspection that this draft comment was likely wrong and/or not actionable:
  This is a Next.js API route handler, and in Next.js 13+, route handlers can receive params as a Promise. The change actually makes the code MORE correct by properly handling the Promise nature of params. The comment is suggesting to revert to the old, incorrect way.
  Maybe there's a way to handle the params Promise differently that would be more idiomatic in Next.js? Maybe I'm not familiar with the latest Next.js best practices?
  No, this is a well-documented Next.js 13+ behavior where route params can be Promises and must be awaited. The change is following the correct pattern.
  The comment should be deleted because it's suggesting to remove a necessary Promise wrapper that is actually the correct pattern for Next.js route handlers.

2. frontend/app/api/projects/[projectId]/traces/workshop/[pipelineVersionId]/route.ts:8

• Draft comment:
  The use of Promise for params in the function signature is unnecessary. You can directly destructure params without wrapping it in a Promise. This pattern is repeated across multiple files.
• Reason this comment was not posted:
  Marked as duplicate.

3. frontend/app/api/workspaces/[workspaceId]/invite/route.ts:11

• Draft comment:
  The use of Promise for params in the function signature is unnecessary. You can directly destructure params without wrapping it in a Promise. This pattern is repeated across multiple files.
• Reason this comment was not posted:
  Marked as duplicate.

4. frontend/app/api/workspaces/[workspaceId]/route.ts:6

• Draft comment:
  The use of Promise for params in the function signature is unnecessary. You can directly destructure params without wrapping it in a Promise. This pattern is repeated across multiple files.
• Reason this comment was not posted:
  Marked as duplicate.

5. frontend/app/api/workspaces/[workspaceId]/update-seats/route.ts:11

• Draft comment:
  The use of Promise for params in the function signature is unnecessary. You can directly destructure params without wrapping it in a Promise. This pattern is repeated across multiple files.
• Reason this comment was not posted:
  Marked as duplicate.

6. frontend/app/blog/[slug]/page.tsx:14

• Draft comment:
  The use of Promise for params in the function signature is unnecessary. You can directly destructure params without wrapping it in a Promise. This pattern is repeated across multiple files.
• Reason this comment was not posted:
  Marked as duplicate.

7. frontend/app/checkout/page.tsx:10

• Draft comment:
  The use of Promise for searchParams in the function signature is unnecessary. You can directly destructure searchParams without wrapping it in a Promise. This pattern is repeated across multiple files.
• Reason this comment was not posted:
  Marked as duplicate.

8. frontend/app/checkout/portal/page.tsx:10

• Draft comment:
  The use of Promise for searchParams in the function signature is unnecessary. You can directly destructure searchParams without wrapping it in a Promise. This pattern is repeated across multiple files.
• Reason this comment was not posted:
  Marked as duplicate.

Workflow ID: wflow_Nz4Ef0G2bYdy8VzJ

---

You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.