Skip to content

Add Empty Nebula project shell #7357

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 17, 2025
Merged

Conversation

MananTank
Copy link
Member

@MananTank MananTank commented Jun 17, 2025


PR-Codex overview

This PR introduces a new Page and Layout component for a Next.js application, along with updates to the TypeScript configuration and package dependencies.

Detailed summary

  • Added Page component in apps/nebula/src/app/page.tsx that renders a simple div with "Test".
  • Created Layout component in apps/nebula/src/app/layout.tsx for wrapping children in a structured HTML layout.
  • Updated tsconfig.json with new compiler options.
  • Modified package.json to include additional dependencies and scripts for development and building.
  • Updated pnpm-lock.yaml to reflect changes in dependencies.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

Summary by CodeRabbit

  • New Features

    • Introduced a new application with a basic layout and a test page displaying sample text.
  • Chores

    • Added initial project configuration files, including TypeScript settings and package management setup.

Copy link

changeset-bot bot commented Jun 17, 2025

⚠️ No Changeset found

Latest commit: 6d62f05

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link
Contributor

coderabbitai bot commented Jun 17, 2025

Walkthrough

New foundational files were added to the apps/nebula directory, initializing a Next.js TypeScript application. These include TypeScript configuration, Next.js type declarations, project metadata and dependencies, and basic React components for the application's layout and main page.

Changes

File(s) Change Summary
apps/nebula/next-env.d.ts Added Next.js TypeScript environment declaration file with references to Next.js and image types.
apps/nebula/package.json Added project metadata, scripts, dependencies, and devDependencies for the Nebula app.
apps/nebula/tsconfig.json Added TypeScript configuration targeting ES2017, integrating with Next.js, and specifying included/excluded files.
apps/nebula/src/app/layout.tsx, apps/nebula/src/app/page.tsx Added default exported React components for application layout and main page.

Sequence Diagram(s)

sequenceDiagram
    participant Browser
    participant Layout
    participant Page

    Browser->>Layout: Render <Layout>{children}</Layout>
    Layout->>Page: Render <Page />
    Page-->>Layout: Return <div>Test</div>
    Layout-->>Browser: Return HTML structure with children
Loading

Suggested labels

Portal

Warning

Review ran into problems

🔥 Problems

Errors were encountered while retrieving linked issues.

Errors (1)
  • TEAM-0000: Entity not found: Issue - Could not find referenced Issue.
✨ Finishing Touches
  • 📝 Generate Docstrings

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

vercel bot commented Jun 17, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
docs-v2 ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 17, 2025 4:32pm
login ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 17, 2025 4:32pm
thirdweb_playground ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 17, 2025 4:32pm
thirdweb-www ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 17, 2025 4:32pm
wallet-ui ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 17, 2025 4:32pm

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (4)
apps/nebula/package.json (2)

41-44: Move Prettier to devDependencies

prettier is a formatting tool and never executes at runtime. Shipping it with production code inflates install size and can slow cold starts for serverless targets.

-    "prettier": "3.5.3",

and re-add it under the existing devDependencies block.


18-55: Version-pinning style is inconsistent

Most packages are caret-pinned (^), some are exact, and a few are workspace ranges. Inconsistent semantics make automated upgrades harder to reason about. Consider adopting one convention (e.g., exact for prod deps, caret for dev) and documenting it in CONTRIBUTING.md.

apps/nebula/src/app/layout.tsx (1)

1-10: Consider extracting children type to avoid implicit React namespace

Referencing React.ReactNode works because @types/react augments the global namespace, but importing the type keeps the file tree-shakable and future-proofs it against possible compiler option changes:

-import React from "react"; // type-only import keeps bundle size zero
-export default function Layout(props: {
-  children: React.ReactNode;
-}) {
+import type { ReactNode } from "react";
+export default function Layout({ children }: { children: ReactNode }) {
   return (
     <html lang="en" suppressHydrationWarning>
       <head>
         <link rel="icon" href="/favicon.ico" />
       </head>
-      <body>{props.children}</body>
+      <body>{children}</body>
     </html>
   );
 }
apps/nebula/src/app/page.tsx (1)

1-3: Stub page is fine, but add a TODO for real content

A single “Test” div is expected in a scaffold. Drop a TODO so the placeholder doesn’t survive to production.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 508b4c4 and 6d62f05.

⛔ Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (5)
  • apps/nebula/next-env.d.ts (1 hunks)
  • apps/nebula/package.json (1 hunks)
  • apps/nebula/src/app/layout.tsx (1 hunks)
  • apps/nebula/src/app/page.tsx (1 hunks)
  • apps/nebula/tsconfig.json (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (8)
  • GitHub Check: E2E Tests (pnpm, vite)
  • GitHub Check: E2E Tests (pnpm, esbuild)
  • GitHub Check: E2E Tests (pnpm, webpack)
  • GitHub Check: Size
  • GitHub Check: Unit Tests
  • GitHub Check: Build Packages
  • GitHub Check: Lint Packages
  • GitHub Check: Analyze (javascript)
🔇 Additional comments (2)
apps/nebula/tsconfig.json (1)

9-14: Type safety is effectively disabled

allowJs: true, skipLibCheck: true, and strict: false turn off most of the TypeScript safety net. If this is only to get the initial shell compiling, add a follow-up ticket to tighten the compiler options once the codebase grows; otherwise subtle bugs will sneak in unchecked.

apps/nebula/next-env.d.ts (1)

1-5: LGTM – standard Next.js boilerplate

No issues spotted.

Copy link
Contributor

size-limit report 📦

Path Size Loading time (3g) Running time (snapdragon) Total time
thirdweb (esm) 62.49 KB (0%) 1.3 s (0%) 287 ms (+98.22% 🔺) 1.6 s
thirdweb (cjs) 350.88 KB (0%) 7.1 s (0%) 1.3 s (+1.53% 🔺) 8.3 s
thirdweb (minimal + tree-shaking) 5.7 KB (0%) 114 ms (0%) 108 ms (+1142.05% 🔺) 222 ms
thirdweb/chains (tree-shaking) 531 B (0%) 11 ms (0%) 47 ms (+1089.8% 🔺) 58 ms
thirdweb/react (minimal + tree-shaking) 19.59 KB (0%) 392 ms (0%) 66 ms (+232.23% 🔺) 458 ms

@jnsdls jnsdls merged commit 85b21ec into main Jun 17, 2025
23 of 24 checks passed
@jnsdls jnsdls deleted the 06-17-add_empty_nebula_project_shell branch June 17, 2025 16:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants