@@ -20,21 +20,19 @@ sf --version # 0.1.0
2020
2121### Setup
2222
23- - Install [ Deno] ( https://docs.deno.com/runtime/ )
24- - ` 2.2.3 `
25- - Install dependencies ` deno install `
26- - Use same mental model as ` npm install `
27- - Auth your CLI with ` deno run prod login `
23+ - Install [ Node.js] ( https://nodejs.org/ ) (v22 or later) - used as the runtime
24+ - Install [ Bun] ( https://bun.sh/ ) - used as the package manager
25+ - Install dependencies: ` bun install `
26+ - Auth your CLI with ` bun run prod login `
2827
2928### Development Loop
3029
3130- Make code changes
3231- Test changes with
33- - ` deno run devv ` to test against local API
34- - ` deno run prod ` to test against production API
35- - The ` deno run <env> ` is an alias to the user facing ` sf ` command. So if you
36- wanted to run ` sf login ` locally against the local API, run
37- ` deno run devv login `
32+ - ` bun run dev ` to test against local API
33+ - ` bun run prod ` to test against production API
34+ - These are aliases to the user facing ` sf ` command. So if you wanted to run
35+ ` sf login ` locally against the local API, run ` bun run dev login `
3836
3937## New Release
4038
@@ -78,10 +76,9 @@ Releases are managed through GitHub Actions. To create a new release:
7876The workflow will:
7977
8078- Run quality checks:
81- - Format checking with ` deno fmt `
82- - Linting with ` deno lint `
83- - Type checking with ` deno check `
84- - Run all tests with ` deno test --allow-all `
79+ - Linting with ` biome ci `
80+ - Type checking with ` tsc --noEmit `
81+ - Run all tests with ` vitest `
8582- Bump the version in package.json
8683- Create a new GitHub release with compiled binaries
8784- Push the version bump commit back to main
0 commit comments