[API] Init API wrapper package #7684

joaquim-verges · 2025-07-23T00:38:10Z

PR-Codex overview

This PR introduces a new API wrapper for @thirdweb-dev/api, enhancing client configuration, request handling, and serialization methods for better interaction with the thirdweb API.

Detailed summary

Added openapi-ts configuration for auto-generating API client.
Introduced types and utility functions for authentication and request handling.
Enhanced body and query serialization methods.
Created client methods for contract and wallet operations.
Updated README with usage examples and configuration instructions.

The following files were skipped due to too many changes: packages/api/src/client/sdk.gen.ts, packages/api/src/client/types.gen.ts

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

Summary by CodeRabbit

New Features
- Introduced the @thirdweb-dev/api package, offering a TypeScript client wrapper for the thirdweb API.
- Added extensive blockchain and wallet management capabilities: contract deployment, wallet creation, transactions, authentication, and token operations.
- Provided utilities for configuring API clients with project secrets and client IDs.
Documentation
- Added a comprehensive README with configuration guidance and example usage.
Chores
- Added TypeScript, linting, and OpenAPI client generation configurations to support development and maintain code quality.

vercel · 2025-07-23T00:38:12Z

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	Jul 23, 2025 1:36am
nebula	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 23, 2025 1:36am
thirdweb_playground	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 23, 2025 1:36am
thirdweb-www	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 23, 2025 1:36am
wallet-ui	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 23, 2025 1:36am

changeset-bot · 2025-07-23T00:38:14Z

🦋 Changeset detected

Latest commit: fb8812e

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@thirdweb-dev/api	Patch

Not sure what this means? Click here to learn what changesets are.

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

coderabbitai · 2025-07-23T00:38:16Z

Walkthrough

This change introduces a new TypeScript package, @thirdweb-dev/api, which provides a generated API client based on the thirdweb OpenAPI specification. The package includes client factory and utility code, type definitions, authentication helpers, parameter and path serialization logic, and a comprehensive SDK for blockchain and wallet operations. Supporting files for configuration, documentation, linting, and build are also added.

Changes

File(s)	Change Summary
.changeset/great-flowers-boil.md	Added a changeset file documenting a patch update for the new API package.
packages/api/README.md	Added a README with usage instructions and example for the API client.
packages/api/biome.json	Added Biome linter configuration for the package.
packages/api/openapi-ts.config.ts	Added OpenAPI TypeScript client generator configuration.
packages/api/package.json	Added package metadata, dependencies, build scripts, and exports for the new package.
packages/api/tsconfig.base.json packages/api/tsconfig.build.json packages/api/tsconfig.json	Added TypeScript configuration files for build, base, and development.
packages/api/src/client/client.gen.ts	Added auto-generated client instance and type alias for client config.
packages/api/src/client/client/client.ts	Added HTTP client factory function with request/response methods and interceptors.
packages/api/src/client/client/index.ts	Added centralized re-exports for client types and utilities.
packages/api/src/client/client/types.ts	Added comprehensive client and request/response type definitions.
packages/api/src/client/client/utils.ts	Added utilities for URL building, query/path serialization, header merging, and interceptors.
packages/api/src/client/core/auth.ts	Added authentication types and token resolution utility.
packages/api/src/client/core/bodySerializer.ts	Added body and query serializer utilities for JSON, FormData, and URL-encoded formats.
packages/api/src/client/core/params.ts	Added parameter mapping and client parameter construction logic.
packages/api/src/client/core/pathSerializer.ts	Added serialization logic for OpenAPI-style query/path parameters.
packages/api/src/client/core/types.ts	Added core client and config type definitions.
packages/api/src/client/index.ts	Added auto-generated entry point re-exporting SDK and types.
packages/api/src/client/sdk.gen.ts	Added auto-generated SDK functions for blockchain, wallet, and authentication API endpoints.
packages/api/src/configure.ts	Added configuration utility, custom JSON serializer, and response type guards.
packages/api/src/exports/thirdweb.ts	Added centralized export module for client config, types, and utilities.

Sequence Diagram(s)

sequenceDiagram
    participant UserApp
    participant APIClient
    participant HTTPClient
    participant BackendAPI

    UserApp->>APIClient: configure({ secretKey, clientId })
    UserApp->>APIClient: call SDK function (e.g., writeContract)
    APIClient->>HTTPClient: build request (auth, headers, params)
    HTTPClient->>BackendAPI: HTTP request (method, path, body)
    BackendAPI-->>HTTPClient: HTTP response (data or error)
    HTTPClient-->>APIClient: parse/transform/validate response
    APIClient-->>UserApp: return result (data or error)

Estimated code review effort

4 (~90 minutes)

The package introduces a moderate-to-high amount of new, mostly auto-generated and utility-heavy code, including complex type definitions, serialization logic, and a broad SDK surface. While many files are generated or boilerplate, several utility and client files warrant careful review for correctness and security. The review effort is substantial but not maximal, as the code is new and self-contained.

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.

joaquim-verges · 2025-07-23T00:38:26Z

[API] Init API wrapper package #7684 👈 (View in Graphite)
main

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

merge-queue - adds this PR to the back of the merge queue
hotfix - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

_{An organization admin has enabled the Graphite Merge Queue in this repository.} _{Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.}

This stack of pull requests is managed by Graphite. Learn more about stacking.

codecov · 2025-07-23T00:45:51Z

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 56.38%. Comparing base (7562952) to head (4961d84).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #7684   +/-   ##
=======================================
  Coverage   56.38%   56.38%           
=======================================
  Files         908      908           
  Lines       58247    58247           
  Branches     4224     4224           
=======================================
  Hits        32844    32844           
  Misses      25293    25293           
  Partials      110      110

Flag	Coverage Δ
packages	`56.38% <ø> (ø)`

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

github-actions · 2025-07-23T00:48:12Z

size-limit report 📦

Path	Size	Loading time (3g)	Running time (snapdragon)	Total time
thirdweb (esm)	63.33 KB (0%)	1.3 s (0%)	449 ms (+84.98% 🔺)	1.8 s
thirdweb (cjs)	353.19 KB (0%)	7.1 s (0%)	1.9 s (+1.48% 🔺)	9 s
thirdweb (minimal + tree-shaking)	5.7 KB (0%)	114 ms (0%)	186 ms (+1042.23% 🔺)	300 ms
thirdweb/chains (tree-shaking)	526 B (0%)	11 ms (0%)	134 ms (+3024.42% 🔺)	144 ms
thirdweb/react (minimal + tree-shaking)	19.59 KB (0%)	392 ms (0%)	179 ms (+501.42% 🔺)	571 ms

coderabbitai

Actionable comments posted: 8

🧹 Nitpick comments (14)

.changeset/great-flowers-boil.md (1)
2-5: Use a clearer title & proper semver bump for a brand-new package

“Init api wrapper” gives little context and the very first public publish is usually a minor (0.1.0 → 0.2.0) or major (1.0.0) – not a patch.
Consider:
---
"@thirdweb-dev/api": minor
---

Initial release of the typed thirdweb API wrapper.
This surfaces the breaking-change risk and helps downstream consumers scan the changelog more easily.
packages/api/tsconfig.json (1)

4-7: Align path alias with build config

~test/* is useful during dev, but the alias is missing from tsconfig.build.json, so compiled code may emit unresolved paths in declaration files.
Either replicate the mapping in the build config or drop the alias.
packages/api/biome.json (1)
1-27: Exclude generated files from lint fixes

Autogenerated *.gen.ts files will constantly flip-flop under useImportExtensions.
Add an override:
   "overrides": [
+    {
+      "files": ["src/**/*.gen.ts"],
+      "linter": { "enabled": false }
+    },
     {
Prevents noisy diffs and keeps CI fast.
packages/api/README.md (2)
10-14: Avoid hard-coding secrets in examples—recommend environment variables instead

The snippet encourages copying a plaintext secret key directly into code. Consider demonstrating best practice with process env references to discourage accidental key exposure.
-  secretKey: "<PROJECT_SECRET_KEY>",
+  secretKey: process.env.THIRDWEB_SECRET_KEY!,
21-25: Use Authorization header for consistency with client configuration

configure() injects the key automatically, yet the example manually adds an x-secret-key header. This can confuse users about the preferred auth flow. Either drop the header here or document why both patterns exist.
packages/api/openapi-ts.config.ts (1)
4-5: Remote spec makes builds non-deterministic—pin or vendor the OpenAPI JSON

Fetching https://api.thirdweb.com/openapi.json at build time can silently change the generated client without review. Cache the spec in the repo or reference a versioned URL to guarantee reproducible builds.
-  input: "https://api.thirdweb.com/openapi.json",
+  // e.g. commit the spec under tools/openapi/thirdweb-<sha>.json
+  input: "./openapi/thirdweb-v2024-07-22.json",
packages/api/src/exports/thirdweb.ts (1)

1-8: Missing public TSDoc on exported surface

Exports under src/exports/** must include comprehensive TSDoc with @example blocks per project guidelines. Add module-level docs explaining when to use configure, the default client, and the type aliases.

packages/api/tsconfig.base.json (1)

15-18: Duplicate comment block—please trim

Lines 4-6 and 15-17 repeat the same note about incremental builds. Removing the duplicate keeps the config concise.
packages/api/src/client/client/index.ts (1)
3-9: Consider omitting file extensions in TS import specifiers

"./client.js" and other .js suffixed paths work under moduleResolution: "NodeNext", but they break if this code is transpiled to CommonJS or consumed with classic resolution. Omitting the extension keeps the specifier portable:
-export { createClient } from "./client.js";
+export { createClient } from "./client";
packages/api/src/configure.ts (1)
20-34: Consider restricting the any type parameter.

The stringify function uses any for the value parameter, which could be more type-safe. Consider using unknown or a more specific type.
-function stringify(
-	value: any,
-	replacer?: ((this: any, key: string, value: any) => any) | null,
-	space?: string | number,
-) {
+function stringify(
+	value: unknown,
+	replacer?: ((this: unknown, key: string, value: unknown) => unknown) | null,
+	space?: string | number,
+) {
packages/api/src/client/client/client.ts (3)
12-16: Consider using a generic type parameter instead of any for the body.

The any type for body in ReqInit reduces type safety. Consider using a generic type parameter or a union type to maintain type safety while supporting various body types.
-type ReqInit = Omit<RequestInit, "body" | "headers"> & {
-	body?: any;
+type ReqInit<T = unknown> = Omit<RequestInit, "body" | "headers"> & {
+	body?: T;
 	headers: ReturnType<typeof mergeHeaders>;
 };
106-123: Consider using generics for better type safety in response data.

The any type for data reduces type safety. Consider using generics to maintain type information through the parsing process.

This would require propagating a generic type parameter through the client interface, allowing consumers to specify expected response types for better compile-time safety.

164-171: Address the TODO comment about error handling.

The TODO indicates that error handling and types need improvement. This should be addressed to provide better error information to consumers.

Would you like me to help implement improved error handling with proper typing and error response structure?
packages/api/src/client/sdk.gen.ts (1)

229-254: Consider consistent parameter patterns across functions.

Some functions like getContractTransactions require the options parameter while others make it optional. Since all functions need at least the URL path parameters, consider making the pattern consistent.

For functions that require path parameters, the current pattern of required options is correct. However, the inconsistency might be confusing for API consumers. Consider documenting this distinction in the README or function comments.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 7562952 and 4961d84.

⛔ Files ignored due to path filters (1)

pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (22)

.changeset/great-flowers-boil.md (1 hunks)
packages/api/README.md (1 hunks)
packages/api/biome.json (1 hunks)
packages/api/openapi-ts.config.ts (1 hunks)
packages/api/package.json (1 hunks)
packages/api/src/client/client.gen.ts (1 hunks)
packages/api/src/client/client/client.ts (1 hunks)
packages/api/src/client/client/index.ts (1 hunks)
packages/api/src/client/client/types.ts (1 hunks)
packages/api/src/client/client/utils.ts (1 hunks)
packages/api/src/client/core/auth.ts (1 hunks)
packages/api/src/client/core/bodySerializer.ts (1 hunks)
packages/api/src/client/core/params.ts (1 hunks)
packages/api/src/client/core/pathSerializer.ts (1 hunks)
packages/api/src/client/core/types.ts (1 hunks)
packages/api/src/client/index.ts (1 hunks)
packages/api/src/client/sdk.gen.ts (1 hunks)
packages/api/src/configure.ts (1 hunks)
packages/api/src/exports/thirdweb.ts (1 hunks)
packages/api/tsconfig.base.json (1 hunks)
packages/api/tsconfig.build.json (1 hunks)
packages/api/tsconfig.json (1 hunks)

📓 Path-based instructions (2)

**/*.{ts,tsx}

📄 CodeRabbit Inference Engine (CLAUDE.md)

**/*.{ts,tsx}: Write idiomatic TypeScript with explicit function declarations and return types
Limit each file to one stateless, single-responsibility function for clarity
Re-use shared types from @/types or local types.ts barrels
Prefer type aliases over interface except for nominal shapes
Avoid any and unknown unless unavoidable; narrow generics when possible
Choose composition over inheritance; leverage utility types (Partial, Pick, etc.)
Comment only ambiguous logic; avoid restating TypeScript in prose

Files:

packages/api/src/client/index.ts
packages/api/openapi-ts.config.ts
packages/api/src/exports/thirdweb.ts
packages/api/src/client/client.gen.ts
packages/api/src/client/client/index.ts
packages/api/src/client/client/client.ts
packages/api/src/client/core/types.ts
packages/api/src/client/core/params.ts
packages/api/src/configure.ts
packages/api/src/client/core/auth.ts
packages/api/src/client/core/pathSerializer.ts
packages/api/src/client/core/bodySerializer.ts
packages/api/src/client/client/utils.ts
packages/api/src/client/client/types.ts
packages/api/src/client/sdk.gen.ts

**/*.{ts,tsx,js,jsx}

📄 CodeRabbit Inference Engine (CLAUDE.md)

Load heavy dependencies inside async paths to keep initial bundle lean (lazy loading)

Files:

packages/api/src/client/index.ts
packages/api/openapi-ts.config.ts
packages/api/src/exports/thirdweb.ts
packages/api/src/client/client.gen.ts
packages/api/src/client/client/index.ts
packages/api/src/client/client/client.ts
packages/api/src/client/core/types.ts
packages/api/src/client/core/params.ts
packages/api/src/configure.ts
packages/api/src/client/core/auth.ts
packages/api/src/client/core/pathSerializer.ts
packages/api/src/client/core/bodySerializer.ts
packages/api/src/client/client/utils.ts
packages/api/src/client/client/types.ts
packages/api/src/client/sdk.gen.ts

🧠 Learnings (22)

📓 Common learnings

Learnt from: CR
PR: thirdweb-dev/js#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-18T19:19:55.613Z
Learning: Surface breaking changes prominently in PR descriptions

Learnt from: CR
PR: thirdweb-dev/js#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-18T19:19:55.613Z
Learning: Applies to packages/thirdweb/src/exports/** : Export everything via `exports/` directory, grouped by feature in the SDK public API

Learnt from: MananTank
PR: thirdweb-dev/js#7356
File: apps/nebula/src/app/not-found.tsx:1-1
Timestamp: 2025-06-17T18:30:52.976Z
Learning: In the thirdweb/js project, the React namespace is available for type annotations (like React.FC) without needing to explicitly import React. This is project-specific configuration that differs from typical TypeScript/React setups.

Learnt from: CR
PR: thirdweb-dev/js#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-18T19:19:55.613Z
Learning: Applies to packages/thirdweb/src/wallets/** : EIP-1193, EIP-5792, EIP-7702 standard support in wallet modules

Learnt from: CR
PR: thirdweb-dev/js#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-18T19:19:55.613Z
Learning: Applies to packages/thirdweb/src/wallets/** : Unified `Wallet` and `Account` interfaces in wallet architecture

Learnt from: MananTank
PR: thirdweb-dev/js#7227
File: apps/dashboard/src/app/(app)/(dashboard)/(chain)/[chain_id]/[contractAddress]/modules/components/OpenEditionMetadata.tsx:26-26
Timestamp: 2025-05-30T17:14:25.332Z
Learning: The ModuleCardUIProps interface already includes a client prop of type ThirdwebClient, so when components use `Omit<ModuleCardUIProps, "children" | "updateButton">`, they inherit the client prop without needing to add it explicitly.

Learnt from: CR
PR: thirdweb-dev/js#0
File: .cursor/rules/dashboard.mdc:0-0
Timestamp: 2025-07-18T19:20:32.530Z
Learning: Applies to dashboard/**/*client.tsx : Anything that consumes hooks from `@tanstack/react-query` or thirdweb SDKs.

Learnt from: CR
PR: thirdweb-dev/js#0
File: .cursor/rules/dashboard.mdc:0-0
Timestamp: 2025-07-18T19:20:32.530Z
Learning: Applies to dashboard/**/api/**/*.{ts,tsx} : Co-locate data helpers under `@/api/**` and mark them with "server-only".

Learnt from: CR
PR: thirdweb-dev/js#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-18T19:19:55.613Z
Learning: Applies to packages/thirdweb/src/wallets/** : Support for in-app wallets (social/email login)

Learnt from: CR
PR: thirdweb-dev/js#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-18T19:19:55.613Z
Learning: Applies to packages/thirdweb/src/wallets/** : Smart wallets with account abstraction

Learnt from: CR
PR: thirdweb-dev/js#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-18T19:19:55.613Z
Learning: Applies to packages/thirdweb/src/exports/** : Every public symbol must have comprehensive TSDoc with at least one `@example` block that compiles and custom annotation tags (`@beta`, `@internal`, `@experimental`)

.changeset/great-flowers-boil.md (1)

Learnt from: CR
PR: thirdweb-dev/js#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-18T19:19:55.613Z
Learning: Surface breaking changes prominently in PR descriptions

packages/api/src/client/index.ts (13)

Learnt from: CR
PR: thirdweb-dev/js#0
File: .cursor/rules/dashboard.mdc:0-0
Timestamp: 2025-07-18T19:20:32.530Z
Learning: Applies to dashboard//api//*.{ts,tsx} : Prefix files with import "server-only"; so they never end up in the client bundle.

Learnt from: CR
PR: thirdweb-dev/js#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-18T19:19:55.613Z
Learning: Applies to packages/thirdweb/src/exports/** : Export everything via exports/ directory, grouped by feature in the SDK public API

Learnt from: CR
PR: thirdweb-dev/js#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-18T19:19:55.613Z
Learning: Applies to apps/{dashboard,playground-web}/**/*.{ts,tsx} : Client Components (browser): Begin files with 'use client';

Learnt from: jnsdls
PR: #7363
File: apps/dashboard/src/app/(app)/layout.tsx:63-74
Timestamp: 2025-06-18T02:01:06.006Z
Learning: In Next.js applications, instrumentation files (instrumentation.ts or instrumentation-client.ts) placed in the src/ directory are automatically handled by the framework and included in the client/server bundles without requiring manual imports. The framework injects these files as part of the build process.

Learnt from: CR
PR: thirdweb-dev/js#0
File: .cursor/rules/dashboard.mdc:0-0
Timestamp: 2025-07-18T19:20:32.530Z
Learning: Applies to dashboard/**/*.{ts,tsx} : Export default async functions without 'use client'; – they run on the Node edge.

Learnt from: CR
PR: thirdweb-dev/js#0
File: .cursor/rules/dashboard.mdc:0-0
Timestamp: 2025-07-18T19:20:32.530Z
Learning: Applies to dashboard/**/components/*.client.tsx : Client components must start with 'use client'; before imports.

Learnt from: CR
PR: thirdweb-dev/js#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-18T19:19:55.613Z
Learning: Applies to src/exports/react.native.ts : React Native specific exports are in src/exports/react.native.ts

Learnt from: CR
PR: thirdweb-dev/js#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-18T19:19:55.613Z
Learning: Applies to apps/{dashboard,playground-web}/**/*.{ts,tsx} : Server Components (Node edge): Start files with import "server-only";

Learnt from: CR
PR: thirdweb-dev/js#0
File: .cursor/rules/dashboard.mdc:0-0
Timestamp: 2025-07-18T19:20:32.530Z
Learning: Applies to dashboard//api//*.{ts,tsx} : Co-locate data helpers under @/api/** and mark them with "server-only".

Learnt from: CR
PR: thirdweb-dev/js#0
File: .cursor/rules/dashboard.mdc:0-0
Timestamp: 2025-07-18T19:20:32.530Z
Learning: Applies to dashboard//components//index.ts : Group related components in their own folder and expose a single barrel index.ts where necessary.

Learnt from: CR
PR: thirdweb-dev/js#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-18T19:19:55.613Z
Learning: Applies to src/extensions/** : Auto-generated contracts from ABI definitions in extensions

Learnt from: CR
PR: thirdweb-dev/js#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-18T19:19:55.613Z
Learning: Applies to **/*.{ts,tsx} : Re-use shared types from @/types or local types.ts barrels

Learnt from: CR
PR: thirdweb-dev/js#0
File: .cursor/rules/dashboard.mdc:0-0
Timestamp: 2025-07-18T19:20:32.530Z
Learning: Applies to dashboard/**/*client.tsx : Anything that consumes hooks from @tanstack/react-query or thirdweb SDKs.

packages/api/tsconfig.json (13)

Learnt from: CR
PR: thirdweb-dev/js#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-18T19:19:55.613Z
Learning: Applies to **/*.test.{ts,tsx} : Place tests alongside code: foo.ts ↔ foo.test.ts

Learnt from: CR
PR: thirdweb-dev/js#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-18T19:19:55.613Z
Learning: Applies to **/*.{ts,tsx} : Re-use shared types from @/types or local types.ts barrels

Learnt from: CR
PR: thirdweb-dev/js#0
File: .cursor/rules/dashboard.mdc:0-0
Timestamp: 2025-07-18T19:20:32.530Z
Learning: Applies to dashboard//api//*.{ts,tsx} : Co-locate data helpers under @/api/** and mark them with "server-only".

Learnt from: CR
PR: thirdweb-dev/js#0
File: .cursor/rules/dashboard.mdc:0-0
Timestamp: 2025-07-18T19:20:32.530Z
Learning: Applies to dashboard//api//*.{ts,tsx} : Prefix files with import "server-only"; so they never end up in the client bundle.

Learnt from: CR
PR: thirdweb-dev/js#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-18T19:19:55.613Z
Learning: Applies to **/*.{ts,tsx} : Write idiomatic TypeScript with explicit function declarations and return types

Learnt from: CR
PR: thirdweb-dev/js#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-18T19:19:55.613Z
Learning: Applies to **/*.{ts,tsx} : Prefer type aliases over interface except for nominal shapes

Learnt from: CR
PR: thirdweb-dev/js#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-18T19:19:55.613Z
Learning: Applies to **/*.test.{ts,tsx} : Keep tests deterministic and side-effect free

Learnt from: CR
PR: thirdweb-dev/js#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-18T19:19:55.613Z
Learning: Applies to **/*.{ts,tsx} : Avoid any and unknown unless unavoidable; narrow generics when possible

Learnt from: CR
PR: thirdweb-dev/js#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-18T19:19:55.613Z
Learning: Applies to **/*.{ts,tsx} : Comment only ambiguous logic; avoid restating TypeScript in prose

Learnt from: CR
PR: thirdweb-dev/js#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-18T19:19:55.613Z
Learning: Applies to **/*.{ts,tsx} : Choose composition over inheritance; leverage utility types (Partial, Pick, etc.)

Learnt from: CR
PR: thirdweb-dev/js#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-18T19:19:55.613Z
Learning: Applies to **/*.test.{ts,tsx} : Use Mock Service Worker (MSW) for fetch/HTTP call interception in tests

Learnt from: CR
PR: thirdweb-dev/js#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-18T19:19:55.613Z
Learning: Applies to **/*.test.{ts,tsx} : Use FORKED_ETHEREUM_CHAIN for mainnet interactions and ANVIL_CHAIN for isolated tests

Learnt from: CR
PR: thirdweb-dev/js#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-18T19:19:55.613Z
Learning: Applies to apps/{dashboard,playground-web}/**/*.{ts,tsx} : Server Components (Node edge): Start files with import "server-only";

packages/api/tsconfig.build.json (14)