npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@clerk/dev-cli

v0.0.9

Published

CLI tool designed to simplify the process of iterating on packages within the clerk/javascript repository

Downloads

143

Readme

clerk-dev CLI

The clerk-dev CLI is a tool designed to simplify the process of iterating on packages within the clerk/javascript repository within sample applications, such as customer reproductions. It allows for the installation of the monorepo versions of packages, and supports features such as hot module reloading for increased development velocity.

Installation

npm install --global @clerk/dev-cli

If you haven't already, install turbo globally.

npm install --global turbo

First time setup

After installing @clerk/dev globally, you'll need to initialise a configuration file and tell the CLI where to find your local copy of the clerk/javascript repository.

  1. Initialise the configuration file which will be located at ~/.config/clerk/dev.json:

    ```shell
    clerk-dev init
    ```
  2. Navigate to your local clone of clerk/javascript and run set-root:

    ```shell
    clerk-dev set-root
    ```

You're all set now to run the day-to-day commands 🎉

Adding instances & changing the configuration

During the first time setup a ~/.config/clerk/dev.json file was created. Its object contains a activeInstance and instances key. You can add additional instances by adding a new key to the instances object.

You can use the set-instance command to switch between activeInstance afterwards:

clerk-dev set-instance yourName

Per-Project Setup

In each project you'd like to use with the monorepo versions of Clerk packages, clerk-dev can perform one-time framework setup such as installing the monorepo versions of packages and configuring the framework to use your Clerk keys.

To perform framework setup, run:

clerk-dev setup

If you aren't working on @clerk/clerk-js, and do not want to customize the clerkJSUrl, pass --no-js.

clerk-dev setup --no-js

If you want to skip the installation of monorepo versions of packages, pass --skip-install.

clerk-dev setup --skip-install

Running

Once your project has been configured to use the monorepo versions of your dependencies, you can start the watchers for each dependency by running:

clerk-dev watch

This will run the build task for any @clerk/* packages in the package.json of the current working directory, including any of their dependencies.

If you do not want to start the watcher for @clerk/clerk-js, you can instead pass --no-js.

clerk-dev watch --no-js