@project-ajax/create 0.0.23 → 0.0.24

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@project-ajax/create",
-	"version": "0.0.23",
+	"version": "0.0.24",
 	"description": "Initialize a new Notion Project Ajax extensions repo.",
 	"bin": {
 		"create-ajax": "dist/index.js"

package/template/.examples/oauth-example.ts

@@ -0,0 +1,44 @@
+import { oauth } from "@project-ajax/sdk";
+
+/**
+ * OAuth capabilities let your worker access third-party APIs.
+ *
+ * After deploying your worker, start OAuth from the CLI:
+ *
+ *   npx workers oauth start <capabilityKey>
+ *
+ * Where `capabilityKey` is the OAuth capability’s key (see `npx workers capabilities list`).
+ * Once OAuth completes, the worker runtime exposes the access token via an
+ * environment variable and `accessToken()` reads it for you.
+ */
+
+// Option 1: Notion-managed provider (recommended when available).
+// Notion owns the OAuth app credentials and the backend has pre-configured provider settings.
+export const googleAuth = oauth({
+	name: "google-calendar",
+	provider: "google",
+});
+
+// Option 2: User-managed provider (you own the OAuth app credentials).
+// Keep client credentials in worker secrets and read them from `process.env`.
+export const myCustomAuth = oauth({
+	name: "my-custom-provider",
+	authorizationEndpoint: "https://provider.example.com/oauth/authorize",
+	tokenEndpoint: "https://provider.example.com/oauth/token",
+	scope: "read write",
+	clientId: requireEnv("MY_CUSTOM_OAUTH_CLIENT_ID"),
+	clientSecret: requireEnv("MY_CUSTOM_OAUTH_CLIENT_SECRET"),
+	authorizationParams: {
+		access_type: "offline",
+		prompt: "consent",
+	},
+});
+
+function requireEnv(key: string): string {
+	const value = process.env[key];
+	if (value) {
+		return value;
+	}
+
+	throw new Error(`Missing environment variable "${key}"`);
+}

package/template/README.md

@@ -475,46 +475,28 @@ Remove a secret from your worker.
 npx workers secrets rm API_KEY
 ```
 
-### `npx workers connect`
+### `npx workers oauth`
 
-Commands for managing OAuth connections that store provider tokens as worker
-secrets. Connections appear in your runtime as environment variables (e.g.,
-`process.env.NOTION_OAUTH_GOOGLE`).
+Commands for managing OAuth flows for your worker.
 
-#### `npx workers connect providers`
+#### `npx workers oauth start [capabilityKey]`
 
-List the OAuth providers that are currently available for your workspace.
+Start an OAuth flow for an OAuth capability in your worker. The command opens
+your browser and prints a fallback link if it can’t open automatically.
 
-```shell
-npx workers connect providers
-```
-
-#### `npx workers connect add <provider>`
-
-Start the OAuth flow in your browser for the specified provider. The command
-opens your default browser and also prints a fallback link.
+If `capabilityKey` is omitted, the CLI will list OAuth capabilities for your
+deployed worker and prompt you to select one (TTY only). In non-interactive
+contexts, pass the key explicitly.
 
 ```shell
-npx workers connect add google
-```
-
-#### `npx workers connect list`
+# Start OAuth (interactive picker if capabilityKey is omitted)
+npx workers oauth start
 
-Display all active OAuth connections for the deployed worker. The output
-includes the provider name, the environment variable exposed to your code, and
-when the connection was created.
-
-```shell
-npx workers connect list
+# Start OAuth for a specific OAuth capability
+npx workers oauth start <capabilityKey>
 ```
 
-#### `npx workers connect rm <provider>`
-
-Remove an OAuth connection (and the stored tokens) for the specified provider.
-
-```shell
-npx workers connect rm google
-```
+See the [OAuth example](./.examples/oauth-example.ts) for a complete example.
 
 ### Configuration file