@cosmoops/connect-sdk 0.1.0 → 0.2.0

package/README.md

@@ -211,25 +211,15 @@ cookie, `/session`, `/entitlements`, `/plans`, `/addons`, `/apps`, `/sessions`,
 | --- | --- | --- |
 | `CONNECT_API_KEY` | yes | server-side credential |
 | `CONNECT_CLIENT_ID` | yes | OAuth client id |
-| `NEXT_PUBLIC_CONNECT_CLIENT_ID` | yes | same value, for `<ConnectProvider>` |
 | `CONNECT_APP_URL` | no | non-production Connect instance |
 | `CONNECT_SESSION_COOKIE` | no | session cookie name |
 
 Register `{your origin}/api/connect/callback` as a redirect URI in the service's
 Setup tab — the one step this cannot do for you.
 
-Optional `next.config` wrapper, which warns at config load if the public client
-id is missing (a `NEXT_PUBLIC_*` that isn't set fails silently in the browser):
-
-```ts
-import { withConnect } from "@cosmoops/connect-sdk/next";
-export default withConnect({ });
-```
-
-That is all it does. It does **not** stand in for the route file — Next has no
-plugin API that contributes a route from a package, so
-`app/api/connect/[...connect]/route.ts` has to exist either way. The two are
-independent; using both is just the default setup.
+No `next.config.ts` changes needed, including `transpilePackages`: `dist/` is
+already ES2022 with `"use client"` hoisted, so Turbopack and webpack both
+consume it as-is.
 
 Reading the session server-side — no argument, no `headers()` dance:
 
@@ -280,11 +270,14 @@ Then wrap your app:
 ```tsx
 import { ConnectProvider } from "@cosmoops/connect-sdk/client";
 
-<ConnectProvider clientId={process.env.NEXT_PUBLIC_CONNECT_CLIENT_ID!}>
-  {children}
-</ConnectProvider>
+<ConnectProvider>{children}</ConnectProvider>
 ```
 
+No `clientId` prop needed here either: the default sign-in flow bounces the
+browser to your own `/signin` route, which builds the authorize URL
+server-side. Pass `clientId` only if you also pass `redirectUri`, to build
+that URL yourself instead.
+
 ### Components
 
 ```tsx

package/dist/cjs/cli/init.js

@@ -46,8 +46,6 @@ export { ConnectPlansPage as default } from "@cosmoops/connect-sdk/client";
 const ENV_TEMPLATE = `# CosmoOps Connect - values come from your service's Setup tab.
 CONNECT_API_KEY=
 CONNECT_CLIENT_ID=
-# Same value as CONNECT_CLIENT_ID. Inlined at build time for <ConnectProvider>.
-NEXT_PUBLIC_CONNECT_CLIENT_ID=
 `;
 const SCAFFOLDS = [
     {
@@ -112,7 +110,7 @@ function runInit(argv = []) {
         console.log(`  ${marker}  ${(0, node_path_1.relative)(root, target)}  - ${scaffold.description}`);
     }
     const env = ensureEnv(root);
-    console.log(`  ${env === "skipped" ? "exists " : env === "appended" ? "updated" : "created"}  .env.local  - fill in the three values from your service's Setup tab`);
+    console.log(`  ${env === "skipped" ? "exists " : env === "appended" ? "updated" : "created"}  .env.local  - fill in the two values from your service's Setup tab`);
     // The two steps a scaffolder must not do for you: editing an existing layout
     // means parsing and rewriting JSX someone else wrote, and the redirect URI
     // lives in Connect, not in this repo.
@@ -125,7 +123,7 @@ Three things left, all one-time:
 
        <ConnectProvider>{children}</ConnectProvider>
 
-     No props: it reads NEXT_PUBLIC_CONNECT_CLIENT_ID.
+     No props needed.
 
   2. Add the theme to your global stylesheet, last of the three - Tailwind
      first, HeroUI's token layer next, so these values win:
@@ -140,13 +138,9 @@ Three things left, all one-time:
   3. Register {your origin}/api/connect/callback as a redirect URI in your
      service's Setup tab in Connect.
 
-Optionally, in next.config.ts:
-
-     import { withConnect } from "@cosmoops/connect-sdk/next";
-     export default withConnect({ });
-
-It checks NEXT_PUBLIC_CONNECT_CLIENT_ID at config load - the one variable whose
-absence fails silently in the browser rather than loudly on the server.
+No next.config.ts changes needed - not even transpilePackages: dist/ is
+already ES2022 with "use client" hoisted, so Turbopack and webpack consume it
+as-is.
 
 Then <ConnectPlans />, <ConnectSubscriptionGate>, <ConnectFeatureGate> and the
 rest work anywhere below the provider, and getConnectSession() reads the same

package/dist/cjs/client/provider.js

@@ -24,13 +24,12 @@ const ConnectContext = (0, react_1.createContext)(null);
  * origin, where `createConnectHandler` holds the credential.
  *
  * ```tsx
- * // Next.js - clientId comes from NEXT_PUBLIC_CONNECT_CLIENT_ID
  * <ConnectProvider>
  *   <App />
  * </ConnectProvider>
  * ```
  */
-function ConnectProvider({ clientId = process.env.NEXT_PUBLIC_CONNECT_CLIENT_ID ?? "", basePath = "/api/connect", redirectUri, appUrl = exports.CONNECT_APP_URL, fetch: fetchImpl, children, }) {
+function ConnectProvider({ clientId = "", basePath = "/api/connect", redirectUri, appUrl = exports.CONNECT_APP_URL, fetch: fetchImpl, children, }) {
     // One state cell, not three. `isLoading` is *derived* from "no result yet"
     // rather than set - a `setIsLoading(true)` at the top of an effect is a
     // synchronous setState inside that effect, which cascades an extra render

package/dist/cjs/next/index.js

@@ -41,7 +41,6 @@ exports.createConnectHandlers = createConnectHandlers;
 exports.GET = handle;
 exports.POST = handle;
 exports.getConnectSession = getConnectSession;
-exports.withConnect = withConnect;
 const client_js_1 = require("../server/client.js");
 const handler_js_1 = require("../server/handler.js");
 /**
@@ -66,27 +65,23 @@ const handler_js_1 = require("../server/handler.js");
  * <ConnectProvider>{children}</ConnectProvider>
  * ```
  *
- * Plus one line in `next.config.ts`, which is optional but catches the single
- * misconfiguration that fails silently:
- *
- * ```ts
- * import { withConnect } from "@cosmoops/connect-sdk/next";
- * export default withConnect({});
- * ```
- *
- * Configuration comes from the environment, so none of those files take
- * arguments:
+ * No `next.config.ts` changes needed - configuration comes from the
+ * environment, so neither file takes arguments:
  *
  * | Variable | Required | Purpose |
  * | --- | --- | --- |
  * | `CONNECT_API_KEY` | yes | server-side credential |
  * | `CONNECT_CLIENT_ID` | yes | OAuth client id |
- * | `NEXT_PUBLIC_CONNECT_CLIENT_ID` | yes | same value, for `<ConnectProvider>` |
  * | `CONNECT_APP_URL` | no | non-production Connect instance |
  * | `CONNECT_SESSION_COOKIE` | no | session cookie name |
  *
  * Register `{your origin}/api/connect/callback` as a redirect URI in the
  * service's Setup tab. That is the only step this cannot do for you.
+ *
+ * No `next.config.ts` changes needed either, including `transpilePackages`:
+ * `dist/` is already ES2022 with `"use client"` hoisted to the top of every
+ * browser file, so Turbopack and webpack both consume it as-is - adding the
+ * entry only costs build time.
  */
 const DEFAULT_COOKIE = "connect_session";
 function requireEnv(name) {
@@ -266,45 +261,6 @@ async function getConnectSession(request, options = {}) {
         return null;
     }
 }
-/**
- * `next.config` wrapper.
- *
- * Asserts, at config load, that the public client id is present - the one
- * variable whose absence fails silently in the browser instead of loudly on
- * the server, because `NEXT_PUBLIC_*` is inlined at build time and an unset
- * one simply becomes `undefined`. That is its whole job.
- *
- * In particular it does **not** replace the bridge route, and cannot: Next has
- * no plugin API that contributes a route from a `node_modules` package - the
- * App Router discovers routes by walking your own `app/` directory and nothing
- * else, and a `next.config` rewrite still needs a real route to point at. So
- * `app/api/connect/[...connect]/route.ts` has to exist whether or not you use
- * this wrapper. It is one line, and `npx @cosmoops/connect-sdk init` writes it:
- *
- * ```ts
- * export { GET, POST } from "@cosmoops/connect-sdk/next";
- * ```
- *
- * The two are independent - the route works with a plain config, and this
- * wrapper is useful with no route at all. Using both is just the default setup.
- *
- * It does **not** add this package to `transpilePackages`, and you should not
- * either. `dist/` is already ES2022 with `"use client"` hoisted to the top of
- * every browser file, so Turbopack and webpack both consume it as-is;
- * transpiling it again only costs build time. An earlier version of this
- * wrapper added the entry, which is why it may still be in your config.
- *
- * ```ts
- * import { withConnect } from "@cosmoops/connect-sdk/next";
- * export default withConnect({ });
- * ```
- */
-function withConnect(config = {}) {
-    if (!process.env.NEXT_PUBLIC_CONNECT_CLIENT_ID && process.env.NODE_ENV !== "test") {
-        console.warn("[@cosmoops/connect-sdk] NEXT_PUBLIC_CONNECT_CLIENT_ID is not set - <ConnectProvider> will not be able to start a sign-in.");
-    }
-    return config;
-}
 var handler_js_2 = require("../server/handler.js");
 Object.defineProperty(exports, "createConnectHandler", { enumerable: true, get: function () { return handler_js_2.createConnectHandler; } });
 var client_js_2 = require("../server/client.js");

package/dist/esm/cli/init.js

@@ -41,8 +41,6 @@ export { ConnectPlansPage as default } from "@cosmoops/connect-sdk/client";
 const ENV_TEMPLATE = `# CosmoOps Connect - values come from your service's Setup tab.
 CONNECT_API_KEY=
 CONNECT_CLIENT_ID=
-# Same value as CONNECT_CLIENT_ID. Inlined at build time for <ConnectProvider>.
-NEXT_PUBLIC_CONNECT_CLIENT_ID=
 `;
 const SCAFFOLDS = [
     {
@@ -107,7 +105,7 @@ export function runInit(argv = []) {
         console.log(`  ${marker}  ${relative(root, target)}  - ${scaffold.description}`);
     }
     const env = ensureEnv(root);
-    console.log(`  ${env === "skipped" ? "exists " : env === "appended" ? "updated" : "created"}  .env.local  - fill in the three values from your service's Setup tab`);
+    console.log(`  ${env === "skipped" ? "exists " : env === "appended" ? "updated" : "created"}  .env.local  - fill in the two values from your service's Setup tab`);
     // The two steps a scaffolder must not do for you: editing an existing layout
     // means parsing and rewriting JSX someone else wrote, and the redirect URI
     // lives in Connect, not in this repo.
@@ -120,7 +118,7 @@ Three things left, all one-time:
 
        <ConnectProvider>{children}</ConnectProvider>
 
-     No props: it reads NEXT_PUBLIC_CONNECT_CLIENT_ID.
+     No props needed.
 
   2. Add the theme to your global stylesheet, last of the three - Tailwind
      first, HeroUI's token layer next, so these values win:
@@ -135,13 +133,9 @@ Three things left, all one-time:
   3. Register {your origin}/api/connect/callback as a redirect URI in your
      service's Setup tab in Connect.
 
-Optionally, in next.config.ts:
-
-     import { withConnect } from "@cosmoops/connect-sdk/next";
-     export default withConnect({ });
-
-It checks NEXT_PUBLIC_CONNECT_CLIENT_ID at config load - the one variable whose
-absence fails silently in the browser rather than loudly on the server.
+No next.config.ts changes needed - not even transpilePackages: dist/ is
+already ES2022 with "use client" hoisted, so Turbopack and webpack consume it
+as-is.
 
 Then <ConnectPlans />, <ConnectSubscriptionGate>, <ConnectFeatureGate> and the
 rest work anywhere below the provider, and getConnectSession() reads the same

package/dist/esm/client/provider.js

@@ -12,13 +12,12 @@ const ConnectContext = createContext(null);
  * origin, where `createConnectHandler` holds the credential.
  *
  * ```tsx
- * // Next.js - clientId comes from NEXT_PUBLIC_CONNECT_CLIENT_ID
  * <ConnectProvider>
  *   <App />
  * </ConnectProvider>
  * ```
  */
-export function ConnectProvider({ clientId = process.env.NEXT_PUBLIC_CONNECT_CLIENT_ID ?? "", basePath = "/api/connect", redirectUri, appUrl = CONNECT_APP_URL, fetch: fetchImpl, children, }) {
+export function ConnectProvider({ clientId = "", basePath = "/api/connect", redirectUri, appUrl = CONNECT_APP_URL, fetch: fetchImpl, children, }) {
     // One state cell, not three. `isLoading` is *derived* from "no result yet"
     // rather than set - a `setIsLoading(true)` at the top of an effect is a
     // synchronous setState inside that effect, which cascades an extra render

package/dist/esm/next/index.js

@@ -22,27 +22,23 @@ import { createConnectHandler } from "../server/handler.js";
  * <ConnectProvider>{children}</ConnectProvider>
  * ```
  *
- * Plus one line in `next.config.ts`, which is optional but catches the single
- * misconfiguration that fails silently:
- *
- * ```ts
- * import { withConnect } from "@cosmoops/connect-sdk/next";
- * export default withConnect({});
- * ```
- *
- * Configuration comes from the environment, so none of those files take
- * arguments:
+ * No `next.config.ts` changes needed - configuration comes from the
+ * environment, so neither file takes arguments:
  *
  * | Variable | Required | Purpose |
  * | --- | --- | --- |
  * | `CONNECT_API_KEY` | yes | server-side credential |
  * | `CONNECT_CLIENT_ID` | yes | OAuth client id |
- * | `NEXT_PUBLIC_CONNECT_CLIENT_ID` | yes | same value, for `<ConnectProvider>` |
  * | `CONNECT_APP_URL` | no | non-production Connect instance |
  * | `CONNECT_SESSION_COOKIE` | no | session cookie name |
  *
  * Register `{your origin}/api/connect/callback` as a redirect URI in the
  * service's Setup tab. That is the only step this cannot do for you.
+ *
+ * No `next.config.ts` changes needed either, including `transpilePackages`:
+ * `dist/` is already ES2022 with `"use client"` hoisted to the top of every
+ * browser file, so Turbopack and webpack both consume it as-is - adding the
+ * entry only costs build time.
  */
 const DEFAULT_COOKIE = "connect_session";
 function requireEnv(name) {
@@ -236,44 +232,5 @@ export async function getConnectSession(request, options = {}) {
         return null;
     }
 }
-/**
- * `next.config` wrapper.
- *
- * Asserts, at config load, that the public client id is present - the one
- * variable whose absence fails silently in the browser instead of loudly on
- * the server, because `NEXT_PUBLIC_*` is inlined at build time and an unset
- * one simply becomes `undefined`. That is its whole job.
- *
- * In particular it does **not** replace the bridge route, and cannot: Next has
- * no plugin API that contributes a route from a `node_modules` package - the
- * App Router discovers routes by walking your own `app/` directory and nothing
- * else, and a `next.config` rewrite still needs a real route to point at. So
- * `app/api/connect/[...connect]/route.ts` has to exist whether or not you use
- * this wrapper. It is one line, and `npx @cosmoops/connect-sdk init` writes it:
- *
- * ```ts
- * export { GET, POST } from "@cosmoops/connect-sdk/next";
- * ```
- *
- * The two are independent - the route works with a plain config, and this
- * wrapper is useful with no route at all. Using both is just the default setup.
- *
- * It does **not** add this package to `transpilePackages`, and you should not
- * either. `dist/` is already ES2022 with `"use client"` hoisted to the top of
- * every browser file, so Turbopack and webpack both consume it as-is;
- * transpiling it again only costs build time. An earlier version of this
- * wrapper added the entry, which is why it may still be in your config.
- *
- * ```ts
- * import { withConnect } from "@cosmoops/connect-sdk/next";
- * export default withConnect({ });
- * ```
- */
-export function withConnect(config = {}) {
-    if (!process.env.NEXT_PUBLIC_CONNECT_CLIENT_ID && process.env.NODE_ENV !== "test") {
-        console.warn("[@cosmoops/connect-sdk] NEXT_PUBLIC_CONNECT_CLIENT_ID is not set - <ConnectProvider> will not be able to start a sign-in.");
-    }
-    return config;
-}
 export { createConnectHandler } from "../server/handler.js";
 export { ConnectClient } from "../server/client.js";

package/dist/types/client/provider.d.ts

@@ -7,7 +7,12 @@ export interface ConnectSession {
     serviceRole: ServiceRole | null;
 }
 export interface ConnectContextValue {
-    /** Public OAuth client id. Safe in a browser - it goes in the authorize URL. */
+    /**
+     * Public OAuth client id, if `clientId` was passed to `<ConnectProvider>` -
+     * empty string otherwise. Safe in a browser regardless: it only ever goes
+     * into the authorize URL. Most integrations never read this - it exists for
+     * the explicit-`redirectUri` flow, see `ConnectProviderProps.clientId`.
+     */
     clientId: string;
     /** Connect's own origin, for deep links out to Profile, Billing and the catalog. */
     appUrl: string;
@@ -58,9 +63,11 @@ export interface ConnectProviderProps {
     /**
      * This service's public `client_id`, from its Setup tab in Connect.
      *
-     * Optional in Next.js, where it falls back to `NEXT_PUBLIC_CONNECT_CLIENT_ID`
-     * - inlined at build time, so `<ConnectProvider>` needs no props at all.
-     * Pass it explicitly anywhere that variable does not exist.
+     * Not needed for the default sign-in flow: `signIn()` with no `redirectUri`
+     * bounces the browser to your own `/signin` route, which already knows
+     * `client_id` server-side (`CONNECT_CLIENT_ID`) and builds the authorize URL
+     * itself - the browser never needs it. Pass this only alongside an explicit
+     * `redirectUri`, when you're building that URL yourself instead.
      */
     clientId?: string;
     /** Where `createConnectHandler` is mounted in your app. Must match its `basePath`. */
@@ -91,7 +98,6 @@ export interface ConnectProviderProps {
  * origin, where `createConnectHandler` holds the credential.
  *
  * ```tsx
- * // Next.js - clientId comes from NEXT_PUBLIC_CONNECT_CLIENT_ID
  * <ConnectProvider>
  *   <App />
  * </ConnectProvider>

package/dist/types/next/index.d.ts

@@ -97,40 +97,6 @@ export declare function getConnectSession(request?: Request, options?: {
     client?: ConnectClient;
     session?: ConnectSessionStore;
 }): Promise<UserResponse | null>;
-/**
- * `next.config` wrapper.
- *
- * Asserts, at config load, that the public client id is present - the one
- * variable whose absence fails silently in the browser instead of loudly on
- * the server, because `NEXT_PUBLIC_*` is inlined at build time and an unset
- * one simply becomes `undefined`. That is its whole job.
- *
- * In particular it does **not** replace the bridge route, and cannot: Next has
- * no plugin API that contributes a route from a `node_modules` package - the
- * App Router discovers routes by walking your own `app/` directory and nothing
- * else, and a `next.config` rewrite still needs a real route to point at. So
- * `app/api/connect/[...connect]/route.ts` has to exist whether or not you use
- * this wrapper. It is one line, and `npx @cosmoops/connect-sdk init` writes it:
- *
- * ```ts
- * export { GET, POST } from "@cosmoops/connect-sdk/next";
- * ```
- *
- * The two are independent - the route works with a plain config, and this
- * wrapper is useful with no route at all. Using both is just the default setup.
- *
- * It does **not** add this package to `transpilePackages`, and you should not
- * either. `dist/` is already ES2022 with `"use client"` hoisted to the top of
- * every browser file, so Turbopack and webpack both consume it as-is;
- * transpiling it again only costs build time. An earlier version of this
- * wrapper added the entry, which is why it may still be in your config.
- *
- * ```ts
- * import { withConnect } from "@cosmoops/connect-sdk/next";
- * export default withConnect({ });
- * ```
- */
-export declare function withConnect<T extends object>(config?: T): T;
 export { createConnectHandler } from "../server/handler.js";
 export type { ConnectSessionStore } from "../server/handler.js";
 export { ConnectClient } from "../server/client.js";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cosmoops/connect-sdk",
-  "version": "0.1.0",
+  "version": "0.2.0",
   "description": "Official server-side SDK for the CosmoOps Connect platform API - Login with Connect, entitlements, billing and metering.",
   "license": "SEE LICENSE IN LICENSE",
   "type": "commonjs",