@sst-community/sst 4.17.4 → 4.18.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +7 -0
  2. package/package.json +12 -9
package/README.md CHANGED
@@ -9,10 +9,15 @@ Build full-stack apps on your own infrastructure.
9
9
  > [!NOTE]
10
10
  > **sst-community** is a community-maintained fork of [SST](https://github.com/anomalyco/sst). It is not affiliated with SST or Anomaly. It tracks upstream releases and carries fixes that haven't landed upstream yet.
11
11
  >
12
+ > **It needs Node.js 22 or later**, since 4.18.0.
13
+ >
12
14
  > Releases have their own version numbers, because the fork moves faster than SST: up to 4.17.2 they followed SST's, and from there on the fork's 4.18.0 isn't SST's 4.18.0. Each release's notes say which SST release it's built on and list what it changes, and `sst version` shows the SST release too. Telemetry is off. Docs: [sst-community.github.io/sst](https://sst-community.github.io/sst/docs/). Chat: [Discord](https://discord.gg/DQWT3WGVm2).
13
15
 
14
16
  ## Installation
15
17
 
18
+ > [!IMPORTANT]
19
+ > **Node.js 22 or later is required**, since 4.18.0, everywhere you run `sst`, CI included. SST runs your `sst.config.ts` with Node, even when your app isn't written in JavaScript. On an older Node.js the CLI warns, and some features fail: on Node.js 20, inline Lambda callbacks do.
20
+
16
21
  For JavaScript projects, install the fork locally under the name `sst`, so the CLI version is tracked with your app and `import ... from "sst"` keeps working. You can then run the CLI with the same package manager.
17
22
 
18
23
  ```bash
@@ -24,6 +29,8 @@ npm install sst@npm:@sst-community/sst
24
29
 
25
30
  To switch an existing project from SST, change its dependency to `"sst": "npm:@sst-community/sst@<version>"` and reinstall. `sst upgrade` keeps it pointing at the fork.
26
31
 
32
+ If the project uses the Astro or SvelteKit adapter, switch it the same way, to `"astro-sst": "npm:@sst-community/astro-sst@<version>"` or `"svelte-kit-sst": "npm:@sst-community/svelte-kit-sst@<version>"`. Its imports stay the same. SST's own `astro-sst` 3.x doesn't support Astro 6 or later, and its `svelte-kit-sst` 2.x doesn't support SvelteKit 3. `sst upgrade` doesn't change the adapters.
33
+
27
34
  If you are not using JavaScript, you can install the CLI globally.
28
35
 
29
36
  ```bash
package/package.json CHANGED
@@ -3,7 +3,7 @@
3
3
  "name": "@sst-community/sst",
4
4
  "type": "module",
5
5
  "sideEffects": false,
6
- "version": "4.17.4",
6
+ "version": "4.18.1",
7
7
  "main": "./dist/index.js",
8
8
  "repository": {
9
9
  "type": "git",
@@ -55,19 +55,22 @@
55
55
  "sst": "./bin/sst.mjs"
56
56
  },
57
57
  "optionalDependencies": {
58
- "@sst-community/sst-linux-x64": "4.17.4",
59
- "@sst-community/sst-linux-x86": "4.17.4",
60
- "@sst-community/sst-darwin-x64": "4.17.4",
61
- "@sst-community/sst-linux-arm64": "4.17.4",
62
- "@sst-community/sst-darwin-arm64": "4.17.4",
63
- "@sst-community/sst-win32-x64": "4.17.4",
64
- "@sst-community/sst-win32-x86": "4.17.4",
65
- "@sst-community/sst-win32-arm64": "4.17.4"
58
+ "@sst-community/sst-linux-x64": "4.18.1",
59
+ "@sst-community/sst-linux-x86": "4.18.1",
60
+ "@sst-community/sst-darwin-x64": "4.18.1",
61
+ "@sst-community/sst-linux-arm64": "4.18.1",
62
+ "@sst-community/sst-darwin-arm64": "4.18.1",
63
+ "@sst-community/sst-win32-x86": "4.18.1",
64
+ "@sst-community/sst-win32-x64": "4.18.1",
65
+ "@sst-community/sst-win32-arm64": "4.18.1"
66
66
  },
67
67
  "dependencies": {
68
68
  "@aws/durable-execution-sdk-js": "1.0.2",
69
69
  "aws4fetch": "1.0.18",
70
70
  "jose": "5.2.3",
71
71
  "openid-client": "5.6.4"
72
+ },
73
+ "engines": {
74
+ "node": ">=22"
72
75
  }
73
76
  }