Merged
Conversation
…de formatting and linting
… improved documentation quality
…roved performance
…chema for enhanced type checking
…roved development experience
…endency management
Owner
Author
|
@coderabbitai help |
ChatThere are 3 ways to chat with CodeRabbit:
CodeRabbit commands
Other keywords and placeholders
CodeRabbit configuration file (
|
Owner
Author
|
@coderabbitai review |
✅ Actions performedReview triggered.
|
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Use the checkbox below for a quick retry:
📝 WalkthroughWalkthroughThe PR establishes a comprehensive Next.js development environment with tooling configurations, CI/CD workflows, and a custom landing page. It adds ESLint, Prettier, TypeScript, GitHub Actions workflows, VS Code settings, EditorConfig, and supporting tool configurations. The existing starter page is replaced with a personalized landing page featuring social links. Dependencies and build scripts are updated accordingly. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 7
🧹 Nitpick comments (15)
.markdownlintignore (1)
1-1: Consider ignoring build output directories.
/node_modulesis covered, but.nextand.open-next(the Cloudflare build output) will also be scanned unless explicitly excluded.🧹 Proposed additions
/node_modules +/.next +/.open-next🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In @.markdownlintignore at line 1, Add build output directories to .markdownlintignore so generated files aren't lint-scanned: update the ignore file to include .next and .open-next (alongside the existing /node_modules) by adding lines for ".next" and ".open-next" (or "/.next" and "/.open-next") so the Markdown linter skips Next.js and Cloudflare build outputs.next.config.ts (1)
4-4: Remove the leftover template placeholder comment.
/* config options here */is a copy-paste artifact from the Next.js starter template and should be removed now that a real option (reactCompiler) has been added.🧹 Proposed fix
const nextConfig: NextConfig = { - /* config options here */ reactCompiler: true, };🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@next.config.ts` at line 4, Remove the leftover template comment "/* config options here */" from next.config.ts; locate the comment near the exported config where reactCompiler is defined and delete that placeholder line so only the real configuration (including reactCompiler) remains.wrangler.jsonc (1)
1-8: Remove the duplicate comment block.The JSDoc header referencing the Wrangler docs appears twice (lines 1–4 and 5–8). One copy should be removed.
🧹 Proposed fix
-/** - * For more details on how to configure Wrangler, refer to: - * https://developers.cloudflare.com/workers/wrangler/configuration/ - */ /** * For more details on how to configure Wrangler, refer to: * https://developers.cloudflare.com/workers/wrangler/configuration/ */🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@wrangler.jsonc` around lines 1 - 8, Remove the duplicated JSDoc header block that repeats "For more details on how to configure Wrangler, refer to: https://developers.cloudflare.com/workers/wrangler/configuration/" so only one instance remains at the top of wrangler.jsonc; locate the two identical comment blocks and delete one of them to eliminate the redundancy.tsconfig.json (1)
14-22:isolatedModulesis redundant alongsideverbatimModuleSyntax.TypeScript recommends combining
erasableSyntaxOnlywithverbatimModuleSyntax, which ensures a module contains the appropriate import syntax and that import elision does not take place.verbatimModuleSyntax: truealready enforces all the constraints ofisolatedModules: true, making the latter redundant. Removing it reduces noise in the config.♻️ Proposed fix
- "isolatedModules": true,🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@tsconfig.json` around lines 14 - 22, Remove the redundant "isolatedModules": true setting from tsconfig since "verbatimModuleSyntax": true already enforces the same constraints; update the tsconfig.json by deleting the isolatedModules entry so only "verbatimModuleSyntax": true (and related flags like "erasableSyntaxOnly") remain to avoid duplicate configuration..prettierignore (1)
29-30: Consider removingnext.config.tsfrom the Prettier ignore list.
next.config.tsis a regular TypeScript file with no reason to opt out of formatting. Excluding it means future edits to the config file won't be auto-formatted, which could produce noisy diffs.♻️ Proposed fix
-next.config.ts🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In @.prettierignore around lines 29 - 30, The .prettierignore currently lists "next.config.ts", preventing Prettier from formatting that TypeScript config file; remove the "next.config.ts" entry from .prettierignore so Prettier will format the file on save/CI, then run Prettier (or prettier --check) to ensure the config file is properly formatted; reference the ".prettierignore" entry and the "next.config.ts" filename when making the change and commit the update..gitignore (1)
17-23: Yarn-specific entries are unnecessary for a pnpm project.Since the project uses pnpm (per
.mise.tomland commit messages), the.pnp.*,.yarn/*, and!.yarn/*negation entries are dead rules. They're harmless, but cleaning them out keeps the.gitignorefocused.♻️ Proposed fix
/node_modules /.pnp -.pnp.* -.yarn/* -!.yarn/patches -!.yarn/plugins -!.yarn/releases -!.yarn/versions🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In @.gitignore around lines 17 - 23, Remove Yarn-specific ignore rules from .gitignore: delete the entries matching .pnp, .pnp.*, .yarn/* and the negations like !.yarn/patches, !.yarn/plugins, !.yarn/releases, !.yarn/versions since this repo uses pnpm; keep only pnpm-relevant ignores to avoid dead/gitignore noise and ensure future maintenance is clear (look for the exact symbols ".pnp", ".pnp.*", ".yarn/*", "!.yarn/patches", "!.yarn/plugins", "!.yarn/releases", "!.yarn/versions" in the file).styles/globals.css (1)
10-10: Stylelintscss/at-rule-no-unknownerror on@themeis a false positive — update the Stylelint config.
@themeis a valid Tailwind CSS v4 directive. The linter is applying SCSS rules to this file and doesn't recognise the Tailwind v4@themeat-rule. Add@themeto the ignore list in the Stylelint configuration to suppress the false positive:{ "rules": { "scss/at-rule-no-unknown": [true, { "ignoreAtRules": ["theme", "source"] }] } }🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@styles/globals.css` at line 10, Stylelint is flagging the Tailwind v4 at-rule `@theme` as unknown due to the SCSS rule `scss/at-rule-no-unknown`; update the Stylelint config to add `"theme"` (and `"source"` if needed) to the `ignoreAtRules` array for `scss/at-rule-no-unknown` so the linter accepts Tailwind directives like `@theme`; modify the rule entry (`scss/at-rule-no-unknown`) in your Stylelint configuration to include the ignoreAtRules option with the necessary at-rule names.package.json (1)
28-43: Minor version pinning inconsistency betweentailwindcssand@tailwindcss/postcss.
tailwindcssis pinned to exact4.2.0while@tailwindcss/postcssuses^4(any 4.x). These are tightly coupled packages — a wide range on one but exact on the other could cause version mismatches after updates. Consider aligning them (e.g., both^4.2.0or both exact).🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@package.json` around lines 28 - 43, The package version pinning for tailwind is inconsistent: update either "tailwindcss" or "@tailwindcss/postcss" so both use the same range to avoid mismatches; for example change "tailwindcss": "4.2.0" to "tailwindcss": "^4.2.0" or change "@tailwindcss/postcss": "^4" to "@tailwindcss/postcss": "4.2.0" (make the choice consistent across the two package entries).app/page.tsx (1)
7-11: Consider addingaria-hidden="true"to decorative SVG icons.Each link already has a visible text label, making the SVGs purely decorative. Adding
aria-hidden="true"prevents screen readers from announcing the SVG contents.Example fix (apply to both SVGs)
- <svg className="size-4" fill="currentColor" viewBox="0 0 24 24"> + <svg aria-hidden="true" className="size-4" fill="currentColor" viewBox="0 0 24 24">Also applies to: 16-20
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@app/page.tsx` around lines 7 - 11, The SVGs used as the "icon" property in app/page.tsx are decorative and should not be announced by screen readers; update each SVG element (the JSX node inside the icon: (...) blocks) to include aria-hidden="true" so assistive tech ignores them, and keep the visible text labels on the links unchanged; apply the same change to both SVG occurrences referenced by the icon property.eslint.config.mjs (2)
111-116:.tsextension injsx-filename-extensionallows JSX in non-TSX files.Typically only
.tsxfiles should contain JSX. Including"ts"means ESLint won't warn when JSX appears in plain.tsfiles, which TypeScript itself would reject (unlessjsxis configured in tsconfig). If this is intentional, no action needed.Proposed fix (if unintentional)
"react/jsx-filename-extension": [ "warn", { - extensions: ["ts", "tsx"], + extensions: [".tsx"], }, ],🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@eslint.config.mjs` around lines 111 - 116, The ESLint rule "react/jsx-filename-extension" currently allows extensions ["ts", "tsx"], which permits JSX in plain .ts files; update the rule in eslint.config.mjs (react/jsx-filename-extension) to only include "tsx" so ESLint will warn for JSX in non-TSX files (or alternatively add a comment explaining that allowing "ts" is intentional if you want JSX in .ts files). Ensure the change modifies the extensions array for the react/jsx-filename-extension rule to remove "ts" and keep "tsx" only.
53-53: Replace deprecatedno-return-awaitwith@typescript-eslint/return-await.The
no-return-awaitrule was deprecated in ESLint v8.46.0. Since this project uses@typescript-eslint/parser, the TypeScript ESLint rule provides better coverage by allowingreturn awaitonly in error-handling contexts (e.g., insidetryblocks where rejections are caught bycatch/finally).Proposed fix
- "no-return-await": "error", + "@typescript-eslint/return-await": ["error", "in-try-catch"],🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@eslint.config.mjs` at line 53, Replace the deprecated ESLint rule "no-return-await" with the TypeScript-aware rule "@typescript-eslint/return-await": remove or stop using "no-return-await" and add "@typescript-eslint/return-await": "error" (or same severity) in the config so the parser `@typescript-eslint/parser` handles return-await semantics; ensure only the new rule name is present and there are no conflicting entries for "no-return-await"..github/workflows/pr.yml (1)
7-9: Node.js 25 is a non-LTS (odd-numbered) release line.Node 25 is the "Current" release and will not receive long-term support. If this project targets production on Cloudflare, this is likely fine (Cloudflare Workers have their own runtime), but be aware that Node 25 will reach end-of-life sooner than an LTS version. Consider pinning to Node 22 (LTS) if stability is a concern for CI.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In @.github/workflows/pr.yml around lines 7 - 9, Update the CI Node version to an LTS release by changing the NODE_VERSION env value (currently NODE_VERSION: 25.3.0) to an LTS release such as Node 22 (e.g., 22.x or a specific LTS like 22.20.0) so the workflow uses a stable, supported Node line for CI; leave PNPM_VERSION unchanged and ensure any Node-version-dependent steps in the workflow still work with the new NODE_VERSION..vscode/settings.json (1)
5-7: Potential conflict betweensource.organizeImportsand Prettier import sorting.The project uses
@ianvs/prettier-plugin-sort-imports(configured inprettier.config.mjs) to sort imports. Runningsource.organizeImportson save invokes VS Code's built-in TypeScript import organizer, which can fight with Prettier's import ordering — leading to a save loop or inconsistent results. Similarly,source.sortMembersmay also conflict if Prettier/ESLint perfectionist handles member sorting. Consider removing both to let Prettier and ESLint handle these concerns.Proposed fix
"editor.codeActionsOnSave": { "source.fixAll.eslint": "explicit", "source.fixAll.markdownlint": "explicit", - "source.fixAll.prettier": "explicit", - "source.organizeImports": "explicit", - "source.sortMembers": "explicit" + "source.fixAll.prettier": "explicit" },🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In @.vscode/settings.json around lines 5 - 7, Remove the VS Code auto-organize and member-sorting settings to avoid conflicts with Prettier's import/member sorting plugin: delete the "source.organizeImports" and "source.sortMembers" entries from the workspace settings (leave "source.fixAll.prettier" intact) so Prettier/ESLint handle import and member ordering exclusively.app/layout.tsx (1)
28-31: Prefer Next.js file-based metadata for the favicon.Next.js App Router automatically serves a favicon when you place
favicon.icoin theapp/directory — no manual<head>or<link>tag needed. This approach integrates with Next.js's metadata system and avoids the manual<head>block. If you do keep the manual link, use self-closing JSX syntax (<link … />).Proposed fix (remove manual head)
return ( <html lang="en"> - <head> - <link href="/favicon.ico" rel="icon" type="image/x-icon"></link> - </head> <body🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@app/layout.tsx` around lines 28 - 31, Remove the manual <head> block and the explicit <link href="/favicon.ico" rel="icon" ...> tag in the layout (the <html> / <head> / <link> elements shown) and rely on Next.js App Router serving favicon.ico placed in the app/ directory; if you decide to keep an explicit favicon link instead, convert the <link> to self-closing JSX syntax (<link ... />) to fix invalid JSX..github/dependabot.yml (1)
1-6: Add agithub-actionsecosystem entry to Dependabot.The PR introduces GitHub Actions workflows that pin action versions (e.g.,
actions/checkout@v4,pnpm/action-setup@v4). Without agithub-actionsDependabot entry, these pins will not receive automated updates, leaving potential security patches unmanaged.Proposed addition
version: 2 updates: - package-ecosystem: "npm" directory: "/" schedule: interval: "weekly" + - package-ecosystem: "github-actions" + directory: "/" + schedule: + interval: "weekly"🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In @.github/dependabot.yml around lines 1 - 6, Add a new Dependabot entry for the GitHub Actions ecosystem so action pins get updated; in the top-level updates list add an item with package-ecosystem: "github-actions", directory: "/" (or the workflows directory if different), and schedule (e.g., interval: "weekly") alongside the existing npm entry to ensure actions like actions/checkout@v4 and pnpm/action-setup@v4 are automatically checked for updates.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In @.github/CODEOWNERS:
- Line 5: The CODEOWNERS entry currently contains just the owner handle
"@dandedotdev" which is invalid; update that line to include a path pattern
followed by the owner (format: "<pattern> <owner>") so the rule matches
files—for example use a repository-wide pattern like "*" or "/**" followed by
`@dandedotdev` to make the entry take effect.
In @.github/workflows/check-secrets.yml:
- Around line 17-22: Update the "Install Git Secrets" and "Scan for secrets"
steps to make installation non-interactive and actually register patterns before
scanning: run apt-get update -y and apt-get install -y in the "Install Git
Secrets" step, then initialize git-secrets (git secrets --install) and register
patterns (at minimum git secrets --register-aws and any org-specific patterns
via git secrets --add) before running the scan, and use git secrets
--scan-history (or run both --scan and --scan-history) in the "Scan for secrets"
step to cover history as well as the working tree.
In @.github/workflows/pr.yml:
- Around line 78-80: The "Install dependencies" step currently checks
needs.init.outputs.cache-hit, causing the lint job to reinstall on init
cache-miss; update that step's if condition to reference the lint job's own
cache step output (e.g. steps.<cache_step_id>.outputs.cache-hit != 'true') so
the install runs only when the lint job's cache is a miss—ensure you use the
actual cache step id used in the lint job instead of needs.init.
In @.vscode/settings.json:
- Line 9: Remove the deprecated VS Code ESLint setting
"eslint.experimental.useFlatConfig" from the workspace settings; locate the JSON
key "eslint.experimental.useFlatConfig" and delete that entry (and trailing
comma if needed) so the settings no longer include this no-op/deprecated
configuration.
In `@eslint.config.mjs`:
- Line 48: The ESLint rule name is incorrect: replace the invalid rule
identifier "eslint-plugin-react/jsx-sort-props" with the correct short-form
"react/jsx-sort-props" in the config so ESLint recognizes the rule; locate the
rule entry (the string "eslint-plugin-react/jsx-sort-props") and update it to
"react/jsx-sort-props" while keeping the existing "off" value.
In `@styles/globals.css`:
- Around line 19-23: The body rule currently hardcodes "Arial, Helvetica,
sans-serif" so the theme token --font-sans (which maps to --font-geist-sans) is
never used; update the body font-family to use var(--font-sans) (optionally
followed by the existing fallback stack) so that the CSS variable --font-sans /
--font-geist-sans can be consumed by the body text and allow next/font injection
to take effect.
In `@tsconfig.json`:
- Around line 37-38: Remove the erroneous include entry
".next/dev/types/**/*.ts" from the tsconfig.json include array so only the
standard Next.js generated path ".next/types/**/*.ts" remains; locate the
include list in tsconfig.json and delete the string ".next/dev/types/**/*.ts"
(leave ".next/types/**/*.ts" intact).
---
Nitpick comments:
In @.github/dependabot.yml:
- Around line 1-6: Add a new Dependabot entry for the GitHub Actions ecosystem
so action pins get updated; in the top-level updates list add an item with
package-ecosystem: "github-actions", directory: "/" (or the workflows directory
if different), and schedule (e.g., interval: "weekly") alongside the existing
npm entry to ensure actions like actions/checkout@v4 and pnpm/action-setup@v4
are automatically checked for updates.
In @.github/workflows/pr.yml:
- Around line 7-9: Update the CI Node version to an LTS release by changing the
NODE_VERSION env value (currently NODE_VERSION: 25.3.0) to an LTS release such
as Node 22 (e.g., 22.x or a specific LTS like 22.20.0) so the workflow uses a
stable, supported Node line for CI; leave PNPM_VERSION unchanged and ensure any
Node-version-dependent steps in the workflow still work with the new
NODE_VERSION.
In @.gitignore:
- Around line 17-23: Remove Yarn-specific ignore rules from .gitignore: delete
the entries matching .pnp, .pnp.*, .yarn/* and the negations like
!.yarn/patches, !.yarn/plugins, !.yarn/releases, !.yarn/versions since this repo
uses pnpm; keep only pnpm-relevant ignores to avoid dead/gitignore noise and
ensure future maintenance is clear (look for the exact symbols ".pnp", ".pnp.*",
".yarn/*", "!.yarn/patches", "!.yarn/plugins", "!.yarn/releases",
"!.yarn/versions" in the file).
In @.markdownlintignore:
- Line 1: Add build output directories to .markdownlintignore so generated files
aren't lint-scanned: update the ignore file to include .next and .open-next
(alongside the existing /node_modules) by adding lines for ".next" and
".open-next" (or "/.next" and "/.open-next") so the Markdown linter skips
Next.js and Cloudflare build outputs.
In @.prettierignore:
- Around line 29-30: The .prettierignore currently lists "next.config.ts",
preventing Prettier from formatting that TypeScript config file; remove the
"next.config.ts" entry from .prettierignore so Prettier will format the file on
save/CI, then run Prettier (or prettier --check) to ensure the config file is
properly formatted; reference the ".prettierignore" entry and the
"next.config.ts" filename when making the change and commit the update.
In @.vscode/settings.json:
- Around line 5-7: Remove the VS Code auto-organize and member-sorting settings
to avoid conflicts with Prettier's import/member sorting plugin: delete the
"source.organizeImports" and "source.sortMembers" entries from the workspace
settings (leave "source.fixAll.prettier" intact) so Prettier/ESLint handle
import and member ordering exclusively.
In `@app/layout.tsx`:
- Around line 28-31: Remove the manual <head> block and the explicit <link
href="/favicon.ico" rel="icon" ...> tag in the layout (the <html> / <head> /
<link> elements shown) and rely on Next.js App Router serving favicon.ico placed
in the app/ directory; if you decide to keep an explicit favicon link instead,
convert the <link> to self-closing JSX syntax (<link ... />) to fix invalid JSX.
In `@app/page.tsx`:
- Around line 7-11: The SVGs used as the "icon" property in app/page.tsx are
decorative and should not be announced by screen readers; update each SVG
element (the JSX node inside the icon: (...) blocks) to include
aria-hidden="true" so assistive tech ignores them, and keep the visible text
labels on the links unchanged; apply the same change to both SVG occurrences
referenced by the icon property.
In `@eslint.config.mjs`:
- Around line 111-116: The ESLint rule "react/jsx-filename-extension" currently
allows extensions ["ts", "tsx"], which permits JSX in plain .ts files; update
the rule in eslint.config.mjs (react/jsx-filename-extension) to only include
"tsx" so ESLint will warn for JSX in non-TSX files (or alternatively add a
comment explaining that allowing "ts" is intentional if you want JSX in .ts
files). Ensure the change modifies the extensions array for the
react/jsx-filename-extension rule to remove "ts" and keep "tsx" only.
- Line 53: Replace the deprecated ESLint rule "no-return-await" with the
TypeScript-aware rule "@typescript-eslint/return-await": remove or stop using
"no-return-await" and add "@typescript-eslint/return-await": "error" (or same
severity) in the config so the parser `@typescript-eslint/parser` handles
return-await semantics; ensure only the new rule name is present and there are
no conflicting entries for "no-return-await".
In `@next.config.ts`:
- Line 4: Remove the leftover template comment "/* config options here */" from
next.config.ts; locate the comment near the exported config where reactCompiler
is defined and delete that placeholder line so only the real configuration
(including reactCompiler) remains.
In `@package.json`:
- Around line 28-43: The package version pinning for tailwind is inconsistent:
update either "tailwindcss" or "@tailwindcss/postcss" so both use the same range
to avoid mismatches; for example change "tailwindcss": "4.2.0" to "tailwindcss":
"^4.2.0" or change "@tailwindcss/postcss": "^4" to "@tailwindcss/postcss":
"4.2.0" (make the choice consistent across the two package entries).
In `@styles/globals.css`:
- Line 10: Stylelint is flagging the Tailwind v4 at-rule `@theme` as unknown due
to the SCSS rule `scss/at-rule-no-unknown`; update the Stylelint config to add
`"theme"` (and `"source"` if needed) to the `ignoreAtRules` array for
`scss/at-rule-no-unknown` so the linter accepts Tailwind directives like
`@theme`; modify the rule entry (`scss/at-rule-no-unknown`) in your Stylelint
configuration to include the ignoreAtRules option with the necessary at-rule
names.
In `@tsconfig.json`:
- Around line 14-22: Remove the redundant "isolatedModules": true setting from
tsconfig since "verbatimModuleSyntax": true already enforces the same
constraints; update the tsconfig.json by deleting the isolatedModules entry so
only "verbatimModuleSyntax": true (and related flags like "erasableSyntaxOnly")
remain to avoid duplicate configuration.
In `@wrangler.jsonc`:
- Around line 1-8: Remove the duplicated JSDoc header block that repeats "For
more details on how to configure Wrangler, refer to:
https://developers.cloudflare.com/workers/wrangler/configuration/" so only one
instance remains at the top of wrangler.jsonc; locate the two identical comment
blocks and delete one of them to eliminate the redundancy.
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
1 participant
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
Update the project template and content based on the Next.js template.
Summary by CodeRabbit