@clerk/clerk-react

What is @clerk/clerk-react?

@clerk/clerk-react is a React library that provides authentication and user management functionalities. It allows developers to easily integrate user sign-up, sign-in, and profile management into their React applications.

What are @clerk/clerk-react's main functionalities?

User Sign-Up

This feature allows users to sign up for an account. The SignUp component provides a pre-built sign-up form that can be easily integrated into your application.

import { SignUp } from '@clerk/clerk-react';

function App() {
  return (
    <div>
      <SignUp />
    </div>
  );
}

User Sign-In

This feature allows users to sign in to their account. The SignIn component provides a pre-built sign-in form that can be easily integrated into your application.

import { SignIn } from '@clerk/clerk-react';

function App() {
  return (
    <div>
      <SignIn />
    </div>
  );
}

User Profile Management

This feature allows users to manage their profile information. The UserProfile component provides a pre-built user profile management interface that can be easily integrated into your application.

import { UserProfile } from '@clerk/clerk-react';

function App() {
  return (
    <div>
      <UserProfile />
    </div>
  );
}

Authentication Guard

This feature allows you to protect routes and components based on the user's authentication status. The SignedIn and SignedOut components can be used to conditionally render content, and RedirectToSignIn can be used to redirect unauthenticated users to the sign-in page.

import { RedirectToSignIn, SignedIn, SignedOut } from '@clerk/clerk-react';

function App() {
  return (
    <div>
      <SignedIn>
        <h1>Welcome, User!</h1>
      </SignedIn>
      <SignedOut>
        <RedirectToSignIn />
      </SignedOut>
    </div>
  );
}

Other packages similar to @clerk/clerk-react

auth0-react

Auth0 React SDK provides authentication and authorization functionalities similar to @clerk/clerk-react. It allows developers to integrate Auth0's authentication services into their React applications. Compared to @clerk/clerk-react, Auth0 offers a broader range of authentication methods and integrations.

firebase

Firebase provides a comprehensive suite of backend services, including authentication, database, and storage. Firebase Authentication can be used to manage user sign-up, sign-in, and profile management. Compared to @clerk/clerk-react, Firebase offers a more extensive set of backend services beyond just authentication.

next-auth

NextAuth.js is a complete open-source authentication solution for Next.js applications. It provides a flexible and extensible way to handle authentication in Next.js. Compared to @clerk/clerk-react, NextAuth.js is more tailored for Next.js and offers a wide range of authentication providers.

README

TSDX React User Guide

Congrats! You just saved yourself hours of work by bootstrapping this project with TSDX. Let’s get you oriented with what’s here and how to use it.

This TSDX setup is meant for developing React components (not apps!) that can be published to NPM. If you’re looking to build an app, you should use create-react-app, razzle, nextjs, gatsby, or react-static.

If you’re new to TypeScript and React, checkout this handy cheatsheet

Commands

TSDX scaffolds your new library inside /src, and also sets up a Parcel-based playground for it inside /example.

The recommended workflow is to run TSDX in one terminal:

npm start # or yarn start

This builds to /dist and runs the project in watch mode so any edits you save inside src causes a rebuild to /dist.

Then run the example inside another:

cd example
npm i # or yarn to install dependencies
npm start # or yarn start

The default example imports and live reloads whatever is in /dist, so if you are seeing an out of date component, make sure TSDX is running in watch mode like we recommend above. No symlinking required, we use Parcel's aliasing.

To do a one-off build, use npm run build or yarn build.

To run tests, use npm test or yarn test.

Configuration

Code quality is set up for you with prettier, husky, and lint-staged. Adjust the respective fields in package.json accordingly.

Jest

Jest tests are set up to run with npm test or yarn test. This runs the test watcher (Jest) in an interactive mode. By default, runs tests related to files changed since the last commit.

Setup Files

This is the folder structure we set up for you:

/example
  index.html
  index.tsx       # test your component here in a demo app
  package.json
  tsconfig.json
/src
  index.tsx       # EDIT THIS
/test
  blah.test.tsx   # EDIT THIS
.gitignore
package.json
README.md         # EDIT THIS
tsconfig.json

React Testing Library

We do not set up react-testing-library for you yet, we welcome contributions and documentation on this.

Rollup

TSDX uses Rollup v1.x as a bundler and generates multiple rollup configs for various module formats and build settings. See Optimizations for details.

TypeScript

tsconfig.json is set up to interpret dom and esnext types, as well as react for jsx. Adjust according to your needs.

Continuous Integration

Travis

to be completed

Circle

to be completed

Optimizations

Please see the main tsdx optimizations docs. In particular, know that you can take advantage of development-only optimizations:

// ./types/index.d.ts
declare var __DEV__: boolean;

// inside your code...
if (__DEV__) {
  console.log('foo');
}

You can also choose to install and use invariant and warning functions.

Module Formats

CJS, ESModules, and UMD module formats are supported.

The appropriate paths are configured in package.json and dist/index.js accordingly. Please report if any issues are found.

Using the Playground

cd example
npm i # or yarn to install dependencies
npm start # or yarn start

The default example imports and live reloads whatever is in /dist, so if you are seeing an out of date component, make sure TSDX is running in watch mode like we recommend above. No symlinking required!

Deploying the Playground

The Playground is just a simple Parcel app, you can deploy it anywhere you would normally deploy that. Here are some guidelines for manually deploying with the Netlify CLI (npm i -g netlify-cli):

cd example # if not already in the example folder
npm run build # builds to dist
netlify deploy # deploy the dist folder

Alternatively, if you already have a git repo connected, you can set up continuous deployment with Netlify:

netlify init
# build command: yarn build && cd example && yarn && yarn build
# directory to deploy: example/dist
# pick yes for netlify.toml

Named Exports

Per Palmer Group guidelines, always use named exports. Code split inside your React app instead of your React library.

Including Styles

There are many ways to ship styles, including with CSS-in-JS. TSDX has no opinion on this, configure how you like.

For vanilla CSS, you can include it at the root directory and add it to the files section in your package.json, so that it can be imported separately by your users and run through their bundler's loader.

Publishing to NPM

We recommend using np.

Usage with Lerna

When creating a new package with TSDX within a project set up with Lerna, you might encounter a Cannot resolve dependency error when trying to run the example project. To fix that you will need to make changes to the package.json file inside the example directory.

The problem is that due to the nature of how dependencies are installed in Lerna projects, the aliases in the example project's package.json might not point to the right place, as those dependencies might have been installed in the root of your Lerna project.

Change the alias to point to where those packages are actually installed. This depends on the directory structure of your Lerna project, so the actual path might be different from the diff below.

   "alias": {
-    "react": "../node_modules/react",
-    "react-dom": "../node_modules/react-dom"
+    "react": "../../../node_modules/react",
+    "react-dom": "../../../node_modules/react-dom"
   },

An alternative to fixing this problem would be to remove aliases altogether and define the dependencies referenced as aliases as dev dependencies instead. However, that might cause other problems.