Keys not being used in @clerk/react-router middleware

[itzcull]

Hey guys, it looks like the publishable & secret key aren't being used in the clerkMiddleware, this is critical for me since I'm not providing application configuration through environment variables

Notice that loadedOptions is only being referenced destructuring a select few properties

I'm on @clerk/react-router: 2.1.5 and react-router: 7.9.3

javascript/packages/react-router/src/server/clerkMiddleware.ts

Line 36 in 791ff19

const loadedOptions = loadOptions(args, options);

[wobsoriano]

Oh, thanks for reporting. I'm looking into this right now. Thanks!

[wobsoriano]

PR fixing this was merged. It will be available in the next SDK release.

In the meantime, you can test it using this snapshot:

npm i https://pkg.pr.new/@clerk/react-router@7079

[Visible-Radio]

This feels like the same issue, or I'm doing something quite wrong.

npm list @clerk/react-router
---> @clerk/react-router@2.1.6

For context I'm trying to run in cloudflare, so I want to pull the secrets off of the context it sets, not from process.env

import { clerkMiddleware, rootAuthLoader } from '@clerk/react-router/server';
import { cloudflareContext } from './context/cloudflare';


export const middleware: Route.MiddlewareFunction[] = [
  clerkMiddleware({ secretKey: 'foo' }),
];

export const loader = async (args: Route.LoaderArgs) => {
  const { env } = args.context.get(cloudflareContext);

  console.log('In the loader...', { env });

  return rootAuthLoader(args, () => null, {
    secretKey: 'bar',
    publishableKey: 'baz',
    // secretKey: env.CLERK_SECRET_KEY,
    // publishableKey: env.VITE_CLERK_PUBLISHABLE_KEY,
  });
};

npx wrangler dev

 ⛅️ wrangler 4.45.0 (update available 4.45.2)
─────────────────────────────────────────────
Using redirected Wrangler configuration.
 - Configuration being used: "build/server/wrangler.json"
 - Original user's configuration: "wrangler.jsonc"
 - Deploy configuration file: ".wrangler/deploy/config.json"
Using vars defined in .env
Your Worker has access to the following bindings:
Binding                                                         Resource                  Mode
env.VALUE_FROM_CLOUDFLARE ("Hello from Cloudflare 3")           Environment Variable      local
env.VITE_CLERK_PUBLISHABLE_KEY ("(hidden)")                     Environment Variable      local
env.CLERK_SECRET_KEY ("(hidden)")                               Environment Variable      local

╭──────────────────────────────────────────────────────────────────────╮
│  [b] open a browser [d] open devtools [c] clear console [x] to exit  │
╰──────────────────────────────────────────────────────────────────────╯
Attaching additional modules:
┌─────────────────────────────────┬──────┬────────────┐
│ Name                            │ Type │ Size       │
├─────────────────────────────────┼──────┼────────────┤
│ assets/server-build-Bz4PO_Is.js │ esm  │ 739.22 KiB │
├─────────────────────────────────┼──────┼────────────┤
│ assets/worker-entry-CF5F9nTn.js │ esm  │ 244.54 KiB │
├─────────────────────────────────┼──────┼────────────┤
│ Total (2 modules)               │      │ 983.76 KiB │
└─────────────────────────────────┴──────┴────────────┘
⎔ Starting local server...
[wrangler:info] Ready on http://localhost:8787
{
  env: {
    VALUE_FROM_CLOUDFLARE: 'Hello from Cloudflare 3',
    VITE_CLERK_PUBLISHABLE_KEY: 'pk_test_redacted',
    CLERK_SECRET_KEY: 'sk_test_redacted'
  },
  ctx: ExecutionContext { props: {} }
}
✘ [ERROR] Error: 🔒 Clerk: A secretKey must be provided in order to use SSR and the exports from @clerk/react-router/api.');

  If your runtime supports environment variables, you can add a CLERK_SECRET_KEY variable to your
  config.
  Otherwise, you can pass a secretKey parameter to rootAuthLoader or getAuth.
  
  For more info, check out the docs: https://clerk.com/docs,
  or come say hi in our discord server: https://clerk.com/discord