Convex Component Template

This is a Convex component, ready to be published on npm.

To create your own component:

1. Find and replace "@convex-dev/sharded-counter" with your npm package's name.
2. Find and replace "get-convex/sharded-counter" to your component's repo.
3. Find and replace "ShardedCounter", "shardedCounter", "sharded-counter", "sharded_counter", "sharded counter", and "Sharded Counter" to your component's name.
4. Write code in src/component for your component.
5. Write code in src/client for your thick client.
6. Write example usage in example/convex/example.ts.
7. Delete the text in this readme until --- and flesh out the README.

To develop your component run a dev process in the example project.

npm i
cd example
npm i
npx convex dev

Modify the schema and index files in src/component/ to define your component.

Write a client for using this component in src/client/index.ts.

If you won't be adding frontend code (e.g. React components) to this component you can delete the following:

• "prepack" and "postpack" scripts of package.json
• "./react" exports in package.json
• the "src/react/" directory
• the "node10stubs.mjs" file

Component Directory structure

.
├── README.md           documentation of your component
├── package.json        component name, version number, other metadata
├── package-lock.json   Components are like libraries, package-lock.json
│                       is .gitignored and ignored by consumers.
├── src
│   ├── component/
│   │   ├── _generated/ Files here are generated.
│   │   ├── convex.config.ts  Name your component here and use other components
│   │   ├── index.ts    Define functions here and in new files in this directory
│   │   └── schema.ts   schema specific to this component
│   ├── client/index.ts "Thick" client code goes here.
│   └── react/          Code intended to be used on the frontend goes here.
│       │               Your are free to delete this if this component
│       │               does not provide code.
│       └── index.ts
├── example/            example Convex app that uses this component
│   │                   Run 'npx convex dev' from here during development.
│   ├── package.json.ts Thick client code goes here.
│   └── convex/
│       ├── _generated/
│       ├── convex.config.ts  Imports and uses this component
│       ├── myFunctions.ts    Functions that use the component
│       ├── schema.ts         Example app schema
│       └── tsconfig.json
│  
├── dist/               Publishing artifacts will be created here.
├── commonjs.json       Used during build by TypeScript.
├── esm.json            Used during build by TypeScript.
├── node10stubs.mjs     Script used during build for compatibility
│                       with the Metro bundler used with React Native.
├── eslint.config.mjs   Recommended lints for writing a component.
│                       Feel free to customize it.
└── tsconfig.json       Recommended tsconfig.json for writing a component.
                        Some settings can be customized, some are required.

Structure of a Convex Component

A Convex components exposes the entry point convex.config.js. The on-disk location of this file must be a directory containing implementation files. These files should be compiled to ESM. The package.json should contain "type": "module" and the tsconfig.json should contain "moduleResolution": "Bundler" or "Node16" in order to import other component definitions.

In addition to convex.config.js, a component typically exposes a client that wraps communication with the component for use in the Convex environment is typically exposed as a named export MyComponentClient or MyComponent imported from the root package.

import { MyComponentClient } from "my-convex-component";

When frontend code is included it is typically published at a subpath:

import { helper } from "my-convex-component/react";
import { FrontendReactComponent } from "my-convex-component/react";

Frontend code should be compiled as CommonJS code as well as ESM and make use of subpackage stubs (see next section).

If you do include frontend components, prefer peer dependencies to avoid using more than one version of e.g. React.

Support for Node10 module resolution

The Metro bundler for React Native requires setting resolver.unstable_enablePackageExports in order to import code that lives in dist/esm/react.js from a path like my-convex-component/react.

Authors of Convex component that provide frontend components are encouraged to support these legacy "Node10-style" module resolution algorithms by generating stub directories with special pre- and post-pack scripts.

---

Convex Sharded Counter Component

• What is some compelling syntax as a hook?
• Why should you use this component?
• Links to Stack / other resources?

Found a bug? Feature request? File it here.

Pre-requisite: Convex

You'll need an existing Convex project to use the component. Convex is a hosted backend platform, including a database, serverless functions, and a ton more you can learn about here.

Run npm create convex or follow any of the quickstarts to set one up.

Installation

Install the component package:

npm install @convex-dev/sharded-counter

Create a convex.config.ts file in your app's convex/ folder and install the component by calling use:

// convex/convex.config.ts
import { defineApp } from "convex/server";
import shardedCounter from "@convex-dev/sharded-counter/convex.config";

const app = defineApp();
app.use(shardedCounter);

export default app;

Usage

import { components } from "./_generated/api";
import { ShardedCounter } from "@convex-dev/sharded-counter";

const shardedCounter = new ShardedCounter(components.shardedCounter, {
  ...options,
});

See more example usage in example.ts.