@jkomynochecks…feat/node-22-esm-only → feat/coalesce-toolchain-versions-mise-phase-282 files · +519 −726updated 4d agoThis is stacked on #3493.
This PR moves the TypeScript SDK support floor to the latest Node.js 22 release and uses that as the point where we stop carrying custom CommonJS compatibility machinery. The e2e runtime coverage now exercises the latest Node 22, Node 24, and Node 25 lines, so the SDK is tested against the minimum supported version and the newer runtimes users are likely to adopt next.
Because the SDK packages are still on 0.x, the accompanying changeset uses minor bumps while calling out that this is a breaking change inside the existing 0.x line.
It also moves pnpm under mise on this Node 22 layer. That belongs here, not in #3493, because the pinned pnpm@10.28.2 requires Node.js >=22.13. Removing Corepack is intentional: Node.js documents that Corepack is no longer distributed starting with Node.js v25, so relying on corepack enable would keep a toolchain dependency that is already on the way out of the Node distribution.
22.22.3 in mise.toml, mise.lock, toolchain-versions.json, and root devEngines.mise.toml as "npm:pnpm" = "10.28.2", removes the root packageManager / devEngines.packageManager Corepack pin, and removes stale packageManager metadata from real TS packages/examples and generators.corepack enable in the shared setup action and E2E Dockerfiles with mise-managed pnpm or an explicit PNPM_VERSION Docker build arg resolved from mise.22.22.3, 24.16.0, and 25.9.0.tsdown now emits .mjs / .d.mts only and uses the ATTW esm-only profile.require / .cjs / .d.cts package export paths and internal import mappings from the public TS SDK packages.type: module where they were missing it.require('pusher-js') with dynamic ESM import.node/cjs-basic as a modern Node require(esm) interop E2E: it verifies require('@composio/core') works through Node's native ESM loader on Node 22, 24, and 25 while resolving to dist/index.mjs, not a .cjs artifact..cjs / .cts handling from example validation and CLI project-language detection.require(esm) interop and that custom CommonJS compatibility machinery is gone.22.22.3, 24.16.0, 25.9.0 (https://nodejs.org/dist/index.json).mise exec -- pnpm --version -> 10.28.2mise exec -- pnpm install --frozen-lockfilemise exec -- bun run ts/scripts/pre-install/check-toolchain.tsmise exec -- pnpm --filter @e2e-tests/utils typecheckmise exec -- pnpm --filter @e2e-tests/node-cjs-basic typecheckmise exec -- pnpm --filter @e2e-tests/node-cjs-basic test:e2e:nodemise exec -- pnpm --filter @e2e-tests/node-esm-basic typecheckmise exec -- pnpm --filter @composio/cli typecheckmise exec -- pnpm --filter @composio/cli test -- --runInBandmise exec -- pnpm run build:packagesmise exec -- pnpm --filter @composio/cli exec vitest run test/src/services/project-environment-detector.test.tsmise exec -- pnpm exec prettier --check ...docker build -f ts/e2e-tests/_utils/Dockerfile.node --build-arg NODE_VERSION=22.22.3 --build-arg BUN_VERSION=1.3.10 --build-arg PNPM_VERSION=10.28.2 -t composio-e2e-node:pnpm-mise-smoke .docker manifest inspect node:24.16.0-slimdocker manifest inspect node:25.9.0-slimbash -n ts/scripts/create-provider.sh && git diff --checkruby -e "require 'yaml'; YAML.load_file('.github/workflows/ts.test-e2e.yml')"Validated 21 example packages.The latest updates on your projects. Learn more about Vercel for GitHub.
| Project | Deployment | Actions | Updated (UTC) |
|---|---|---|---|
| docs |  Error | Jun 8, 2026 9:57pm |