Upgrade to React 19 and Kinde SDK v5 in TS by DaveOrDead · Pull Request #23 · kinde-starter-kits/react-starter-kit

DaveOrDead · 2025-02-28T11:40:21Z

Explain your changes

Upgrade to React 19 and Kinde SDK v5 in TS

Checklist

I have read the “Pull requests” section in the contributing guidelines.
I agree to the terms within the code of conduct.

🛟 If you need help, consider asking for advice over in the Kinde community.

Summary by CodeRabbit

New Features
- Enhanced authentication experience with simplified login, registration, and logout flows.
- Optimized application startup using updated rendering techniques for smoother performance.
Chores
- Upgraded core libraries—including a major React update—for improved stability.
- Refined build and configuration settings to streamline development and ensure robust type-checking.
- Updated copyright year in the license file.

coderabbitai · 2025-02-28T11:40:28Z

Caution

Review failed

The pull request is closed.

Walkthrough

This pull request introduces numerous configuration and code updates. The .gitignore file has been modified to better manage log files and directories. A new ESLint configuration file has been added to enforce TypeScript and React coding standards. The application’s entry point and HTML file have been updated to reference TypeScript files, and the React rendering now uses the new root API. The project’s version and dependencies in package.json have been upgraded along with the introduction of several TypeScript configuration files and a Vite configuration file. Finally, the authentication components have been simplified by replacing function calls with link components.

Changes

File(s)	Change Summary
`.gitignore`	Log file patterns, directories (`logs`, `.log`, `dist`, `dist-ssr`, `.local`), and IDE/editor files were added. Removed obsolete entries such as dependency/testing markers and previous npm/yarn debug logs.
`eslint.config.js`	Introduced a new TypeScript ESLint configuration that targets `.ts` and `.tsx` files, ignores the `dist` directory, extends recommended ESLint and TypeScript-ESLint settings, and adds plugins for React Hooks and React Refresh.
`index.html`	Updated the document type declaration casing and changed the main script source from `/src/main.jsx` to `/src/main.tsx`.
`package.json`	Updated project version from `1.0.0` to `2.0.0`. Modified the build and lint scripts, upgraded React and authentication dependencies, and overhauled devDependencies by replacing or adding packages including TypeScript, ESLint, and Vite-related tools.
`src/components/LoggedIn.tsx` `src/components/LoggedOut.tsx`	In `LoggedIn.tsx`, removed the `logout` function in favor of the `LogoutLink` component and updated user property names from `given_name`/`family_name` to `givenName`/`familyName`. In `LoggedOut.tsx`, replaced hooks-based login/register functions with `LoginLink` and `RegisterLink` components to simplify authentication calls.
`src/main.tsx`	Modified React imports and rendering logic to utilize `StrictMode` and the new `createRoot` API from `react-dom/client`, and updated the application entry point import from `App.jsx` to `App.tsx`.
`src/vite-env.d.ts` `tsconfig.app.json` `tsconfig.json` `tsconfig.node.json` `vite.config.ts`	Added new TypeScript configuration files defining compiler options, project references, and module settings. Introduced a Vite configuration file that sets up the React plugin and a development server on port 3000; also included a Vite client types reference for improved type checking.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant LoggedOut Component
    participant Auth Service
    User->>LoggedOut Component: Click on LoginLink
    LoggedOut Component->>Auth Service: Initiate login
    Auth Service-->>User: Return authentication response

sequenceDiagram
    participant User
    participant LoggedIn Component
    participant Auth Service
    User->>LoggedIn Component: Click on LogoutLink
    LoggedIn Component->>Auth Service: Initiate logout
    Auth Service-->>User: Return logout confirmation

Poem

I'm a bunny leaping through the code,
Hopping over logs and config mode.
New links for login, logout in view,
TypeScript, React—fresh as dew.
Dependencies soar, errors out of sight,
In every change, my joy takes flight!
🐇 Keep on coding, day and night!

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 132ca42 and c25939a.

⛔ Files ignored due to path filters (1)

package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (4)

.eslintrc.cjs (0 hunks)
LICENSE.md (1 hunks)
package.json (1 hunks)
src/components/LoggedIn.tsx (1 hunks)

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

🪧 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.
- Generate unit testing code for this file.
- 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 generate unit testing code for this file.
- @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 generate unit testing code.
- @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.

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 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.

coderabbitai

Actionable comments posted: 0

🧹 Nitpick comments (2)

tsconfig.app.json (1)

10-12: Inline Comments in JSON Configuration
This section includes inline comments (e.g., /* Bundler mode */). While TypeScript’s configuration files commonly support JSON with comments (JSONC), verify that your development tools and linters are configured to accept them. If any issues arise, consider removing or converting these comments to maintain strict JSON compliance.

🧰 Tools

🪛 Biome (1.9.4)

[error] 10-10: JSON standard does not allow comments.

(parse)

[error] 11-11: End of file expected

Use an array for a sequence of values: [1, 2]

(parse)

[error] 11-11: End of file expected

Use an array for a sequence of values: [1, 2]

(parse)

[error] 11-11: End of file expected

Use an array for a sequence of values: [1, 2]

(parse)

[error] 11-11: End of file expected

Use an array for a sequence of values: [1, 2]

(parse)

[error] 12-12: End of file expected

Use an array for a sequence of values: [1, 2]

(parse)

[error] 12-12: End of file expected

Use an array for a sequence of values: [1, 2]

(parse)

[error] 12-12: End of file expected

Use an array for a sequence of values: [1, 2]

(parse)

[error] 12-12: End of file expected

Use an array for a sequence of values: [1, 2]

(parse)

tsconfig.node.json (1)

9-13: Bundler Mode and Inline Comment Considerations
The inline comment (/* Bundler mode */) improves clarity; however, similar to the application tsconfig, ensure that any tools parsing this file support JSONC.

🧰 Tools

🪛 Biome (1.9.4)

[error] 9-9: JSON standard does not allow comments.

(parse)

[error] 10-10: End of file expected

Use an array for a sequence of values: [1, 2]

(parse)

[error] 10-10: End of file expected

Use an array for a sequence of values: [1, 2]

(parse)

[error] 10-10: End of file expected

Use an array for a sequence of values: [1, 2]

(parse)

[error] 10-10: End of file expected

Use an array for a sequence of values: [1, 2]

(parse)

[error] 11-11: End of file expected

Use an array for a sequence of values: [1, 2]

(parse)

[error] 11-11: End of file expected

Use an array for a sequence of values: [1, 2]

(parse)

[error] 11-11: End of file expected

Use an array for a sequence of values: [1, 2]

(parse)

[error] 11-11: End of file expected

Use an array for a sequence of values: [1, 2]

(parse)

[error] 12-12: End of file expected

Use an array for a sequence of values: [1, 2]

(parse)

[error] 12-12: End of file expected

Use an array for a sequence of values: [1, 2]

(parse)

[error] 12-12: End of file expected

Use an array for a sequence of values: [1, 2]

(parse)

[error] 12-12: End of file expected

Use an array for a sequence of values: [1, 2]

(parse)

[error] 13-13: End of file expected

Use an array for a sequence of values: [1, 2]

(parse)

[error] 13-13: End of file expected

Use an array for a sequence of values: [1, 2]

(parse)

[error] 13-13: End of file expected

Use an array for a sequence of values: [1, 2]

(parse)

[error] 13-13: End of file expected

Use an array for a sequence of values: [1, 2]

(parse)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between c810041 and 132ca42.

⛔ Files ignored due to path filters (1)

package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (12)

.gitignore (1 hunks)
eslint.config.js (1 hunks)
index.html (2 hunks)
package.json (1 hunks)
src/components/LoggedIn.tsx (2 hunks)
src/components/LoggedOut.tsx (1 hunks)
src/main.tsx (2 hunks)
src/vite-env.d.ts (1 hunks)
tsconfig.app.json (1 hunks)
tsconfig.json (1 hunks)
tsconfig.node.json (1 hunks)
vite.config.ts (1 hunks)

✅ Files skipped from review due to trivial changes (4)

vite.config.ts
index.html
src/vite-env.d.ts
tsconfig.json

🧰 Additional context used

🪛 Biome (1.9.4)

tsconfig.app.json

[error] 10-10: JSON standard does not allow comments.

(parse)

[error] 11-11: End of file expected