Skip to content
sst-community
Docs Examples
GitHub Discord

Community fork of SST not affiliated with SST or Anomaly

SST, plus the fixes.

sst-community follows SST's releases and ships fixes that haven't landed upstream yet. Same config, same docs. Only your sst dependency changes.

npm install sst@npm:@sst-community/sst

Needs Node.js 22 or later, wherever you run sst, CI included.

Read the docs Releases GitHub Discord

Switch a project from SST

  1. Use Node.js 22 or later

    node --version should show v22 or later, wherever you run sst, CI included. On an older Node.js the CLI warns, and some features fail.

  2. Run the install in your project

    One line of package.json changes. Your imports and your sst.config.ts stay as they are.

    package.json
    "sst": "<version>"
"sst": "npm:@sst-community/sst@<version>"

    With pnpm, bun or yarn, use add in place of install.

    Using the Astro or SvelteKit adapter? Switch its line the same way, to npm:@sst-community/astro-sst or npm:@sst-community/svelte-kit-sst.

  3. Check which CLI runs

    npx sst version names sst-community and the SST release it's built on.

  4. Deploy as before

    The fork reads the same config and the same state, so sst dev and sst deploy carry on where you left off. sst upgrade keeps you on the fork.

To go back to SST, run npm install sst@latest.