Browser createFrontendClient ignores projectId, causing connect-react calls to use /v1/connect//...

createFrontendClient from @pipedream/sdk/browser appears to ignore a configured projectId.

This looks related to #209 and #281, but the browser-specific client still hardcodes projectId: "".

Tested with:

• @pipedream/sdk@3.0.7
• @pipedream/connect-react@3.0.1

Reproduction:

import { createFrontendClient } from "@pipedream/sdk/browser";

const client = createFrontendClient({
  externalUserId: "user_123",
  projectEnvironment: "development",
  projectId: "proj_expected",
  tokenCallback: async () => ({
    token: "token",
    expiresAt: new Date(Date.now() + 60_000),
    connectLinkUrl: "",
  }),
});

console.log(client._options.projectId); // ""

Observed behavior:

connect-react calls such as client.accounts.list(...) and client.components.list(...) produce URLs like:

https://api.pipedream.com/v1/connect//accounts
https://api.pipedream.com/v1/connect//components

Expected behavior:

The browser client should preserve the configured projectId, or the docs should describe the supported browser-side way for connect-react account/component calls to resolve the project.

Relevant source on current main:

// src/browser/index.ts
super({
  baseUrl,
  projectEnvironment,
  projectId: "",
  tokenProvider,
  workflowDomain,
});

Additional local verification:

Even when passing projectId through public createFrontendClient options, a rendered ComponentForm still attempts account/component requests under /v1/connect//....

Previous related issue/PR:

• #209
• #281

Start in src/browser/index.ts at the createFrontendClient super call, then reproduce the issue with the provided example and inspect the resulting accounts.list or components.list URLs. Done means a configured projectId is preserved for browser client requests, so connect-react calls no longer use /v1/connect//...; compare the behavior with related issues #209 and #281.