Merged
Conversation
jonaslagoni
requested review from
asyncapi-bot-eve,
kennethaasan and
magicmatatjahu
as code owners
✅ Deploy Preview for modelina canceled.
|
- Upgrade next from 13.4.3 to 14.2.35
- Replace `next export` CLI with `output: 'export'` in next.config.js
- Add `images: { unoptimized: true }` for static export compatibility
- Update export script in package.json to use `next build`
Co-Authored-By: Claude <noreply@anthropic.com>
- Upgrade next to 15.5.12, react/react-dom to 19.x - Upgrade TypeScript to 5.x, @types/node to 20, @types/react to latest - Upgrade react-markdown to v9 with rehype-raw@7, rehype-slug@6, remark-gfm@4 - Upgrade @monaco-editor/react to 4.7.0 and framer-motion to latest for React 19 compat - Fix React 19 JSX namespace in Heading.tsx - Fix react-markdown v9 code component API (remove `inline` prop) - Move api utility functions from pages/api/functions/ to src/api-functions/ to fix Next.js 15 API route validation - Fix MonacoEditorWrapper typescript type for deprecated API Co-Authored-By: Claude <noreply@anthropic.com>
- Upgrade next to 16.1.6, @next/bundle-analyzer to 16.x - Remove --no-lint flag from build script (removed in Next.js 16) - eslint.ignoreDuringBuilds already configured in next.config.js - eslint-config-next stays at v15 (v16 requires ESLint 9, separate concern) Co-Authored-By: Claude <noreply@anthropic.com>
- Remove legacyBehavior from Link components in MobileNavMenu.tsx - Remove nested <a> tags inside Link (not needed in Next.js 13+) - Remove unnecessary passHref from Link in Button.tsx Co-Authored-By: Claude <noreply@anthropic.com>
React 19 removed defaultProps support for function components, causing onChange to be undefined and crash in debounce(). Move defaults to destructuring parameter defaults instead. Co-Authored-By: Claude <noreply@anthropic.com>
- Node 16 → 20 (required by Next.js 16) - NPM 8 → 10 (matches Node 20) - publish directory .next → out (static export with output: 'export') Co-Authored-By: Claude <noreply@anthropic.com>
@types/node@22 uses syntax that TypeScript 4.9 cannot parse, causing CI build failures. Upgrade TypeScript to 5.6 and fix type errors: - ConstrainedTypes.ts: cast Set iterator value (unknown → string) - TypeScriptInputProcessor.ts: cast between ts.Program versions (project TS vs typescript-json-schema bundled TS) Co-Authored-By: Claude <noreply@anthropic.com>
@types/node@22 uses syntax that TypeScript 4.9 cannot parse, causing CI build failures. Upgrade TypeScript to 5.6 and fix type errors: - ConstrainedTypes.ts: cast Set iterator value (unknown → string) - TypeScriptInputProcessor.ts: cast between ts.Program versions (project TS vs typescript-json-schema bundled TS) Co-Authored-By: Claude <noreply@anthropic.com>
…ator-model-sdk into upgrade_node_2
integrate-with-next: - Next.js 15 → 16, React 18 → 19, TypeScript 4.9 → 5.6 - Remove unused @next/font dependency - Upgrade @testing-library/dom to v10, jest-dom to v6 - Upgrade @types/node to 22, @types/react to 19 - Update test snapshot for React 19 integrate-with-react: - React 18 → 19 - Upgrade @testing-library/react to v16, user-event to v14 Co-Authored-By: Claude <noreply@anthropic.com>
- Remove cross-env from test script (CI sets CI=true natively) - Regenerate lockfile after ts-jest removal Co-Authored-By: Claude <noreply@anthropic.com>
- Upgrade TypeScript from 4.6.4 to ~5.6.0 - Add cross-env as devDependency (was used but not listed) - Add engines field requiring Node >=22 - Regenerate package-lock.json Co-Authored-By: Claude <noreply@anthropic.com>
|
Contributor
|
🎉 This PR is included in version 6.0.0-next.6 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
Description
Related Issue
Checklist
npm run lint).npm run test).Additional Notes