3.1.2 npm publish dropped the `./browser` and `./server` export subpaths (no matching release in this repo)

Summary

@pipedream/sdk@3.1.2 was published to npm on 2026-07-20, but it removed the ./browser and ./server subpaths from the package exports map. This breaks the exact import that the Pipedream Connect docs instruct users to write:

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

With 3.1.2 installed, any bundler or Node resolution fails with an unresolvable-subpath error, e.g. from Vite/Rolldown:

Error: Errored while resolving "@pipedream/sdk/browser" in `this.resolve`.

Details

Comparing the published tarballs:

3.1.1 exports keys:

".", "./accounts", "./actions", "./appCategories", "./apps", "./browser",
"./components", "./deployedTriggers", "./fileStash", "./oauthTokens",
"./package.json", "./projectEnvironment", "./projects", "./proxy",
"./serialization", "./server", "./tokens", "./triggers", "./usage", "./users"

3.1.2 exports keys:

".", "./accounts", "./actions", "./appCategories", "./apps",
"./components", "./deployedTriggers", "./fileStash", "./oauthTokens",
"./package.json", "./projectEnvironment", "./projects", "./proxy",
"./serialization", "./tokens", "./triggers", "./usage", "./users"

i.e. ./browser and ./server are gone. The browser condition inside the "." export was also removed (3.1.2's "." only has import/require/default).

Notably, the browser build is still shipped in the 3.1.2 tarball (dist/esm/browser/index.mjs with createFrontendClient is present) — it's just no longer reachable through the exports map.

This release doesn't appear to exist in this repo

• There is no 3.1.2 tag or GitHub release here; the latest release is v3.1.1 (2026-06-17).
• main's package.json still says "version": "3.1.1" and still contains the ./browser and ./server export entries.

So it looks like 3.1.2 was published from an automated (Fern?) regeneration pipeline that emitted the stock generated exports map and silently dropped the hand-maintained ./browser / ./server entries, without a corresponding commit landing in this repository.

Impact

• Every project following the documented Connect frontend usage breaks on upgrade to 3.1.2, even though it's a patch release.
• Workaround: pin to 3.1.1 exactly.

Expected

Either:

1. Restore the ./browser and ./server export subpaths (and the browser condition on ".") in a follow-up release, or
2. If the removal is intentional, publish it as a major version with migration guidance and update the Connect docs, which currently still say to import from @pipedream/sdk/browser.

Environment

• @pipedream/sdk@3.1.2 from npm
• Reproduces with any resolver that honors exports (Node 24, Vite 8/Rolldown, Bun)

Start with package.json's exports map and compare the published 3.1.1 and 3.1.2 tarballs, then trace the automated publishing or regeneration path because 3.1.2 has no matching repository release. Done means the browser and server subpaths, plus the browser condition, are preserved in a follow-up release or the documented migration path is updated.