Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

@clerk/chrome-extension

Package Overview
Dependencies
Maintainers
7
Versions
2377
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@clerk/chrome-extension

Clerk SDK for Chrome extensions

  • 0.3.3-staging.2
  • Source
  • npm
  • Socket score

Version published
Weekly downloads
3.3K
decreased by-6.18%
Maintainers
7
Weekly downloads
 
Created
Source


@clerk/chrome-extension

Chat on Discord Clerk documentation Follow on Twitter

Changelog · Report a Bug · Request a Feature · Ask a Question


Overview

Clerk is the easiest way to add authentication and user management to your chrome extension. To gain a better understanding of the Clerk React SDK and Frontend API, refer to the Node SDK and Backend API documentation.

Getting Started

To use this package you should first create a Clerk application and retrieve a Publishable Key for you application to be used as environment variables REACT_APP_CLERK_PUBLISHABLE_KEY.

Prerequisites

  • Node.js v14+

Installation

npm install @clerk/chrome-extension

Usage

Standalone usage snippet:

// App.tsx
import { SignedIn, SignedOut, SignIn, SignUp, ClerkProvider } from '@clerk/chrome-extension';
import { useNavigate, Routes, Route, MemoryRouter } from 'react-router-dom';

function HelloUser() {
  return <p> Hello user</p>;
}

const publishableKey = process.env.REACT_APP_CLERK_PUBLISHABLE_KEY || '';

function ClerkProviderWithRoutes() {
  const navigate = useNavigate();

  return (
    <ClerkProvider
      publishableKey={publishableKey}
      navigate={to => navigate(to)}
    >
      <Routes>
        <Route
          path='/sign-up/*'
          element={<SignUp signInUrl='/' />}
        />
        <Route
          path='/'
          element={
            <>
              <SignedIn>
                <HelloUser />
              </SignedIn>
              <SignedOut>
                <SignIn
                  afterSignInUrl='/'
                  signUpUrl='/sign-up'
                />
              </SignedOut>
            </>
          }
        />
      </Routes>
    </ClerkProvider>
  );
}

function App() {
  return (
    <MemoryRouter>
      <ClerkProviderWithRoutes />
    </MemoryRouter>
  );
}

export default App;

WebSSO usage snippet:

// App.tsx
// use same code with the above & add the syncSessionWithTab prop in <ClerkProvider/>

// ...
<ClerkProvider
  publishableKey={publishableKey}
  navigate={to => navigate(to)}
  syncSessionWithTab
>
  {/* ... */}
</ClerkProvider>
//...

Examples of a chrome extension using the @clerk/chrome-extension package for authentication can be found in our clerk-chrome-extension-starter github repository. The 2 supported cases (links to different branches of the same repository):

  • Standalone: The extension is using its own authentication
  • WebSSO: The extensions shares authentication with a website in the same browser

WebSSO required settings

Permissions (in manifest.json)

Host permissions (in manifest.json)

You will need your Frontend API URL, which can be found in your Dashboard > API Keys > Advanced > Clerk API URLs.

"host_permissions": ["*://YOUR_CLERK_FRONTEND_API_GOES_HERE/"],

Clerk settings

Add your Chrome extension origin to your instance allowed_origins using BAPI:

curl  -X PATCH https://api.clerk.com/v1/instance \
      -H "Authorization: Bearer sk_secret_key" \
      -H "Content-type: application/json" \
      -d '{"allowed_origins": ["chrome-extension://extension_id_goes_here"]}'

Learn More

You can learn more in the Create React App documentation.

To learn React, check out the React documentation.

Support

You can get in touch with us in any of the following ways:

Contributing

We're open to all community contributions! If you'd like to contribute in any way, please read our contribution guidelines.

Security

@clerk/chrome-extension follows good practices of security, but 100% security cannot be assured.

@clerk/chrome-extension is provided "as is" without any warranty. Use at your own risk.

For more information and to report security issues, please refer to our security documentation.

License

This project is licensed under the MIT license.

See LICENSE for more information.

Keywords

FAQs

Package last updated on 23 May 2023

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc