3 Commits

Author	SHA1	Message	Date
Tyler Cloutier	a4d29daec8	Fix spacetime dev template issues and clean up CLI (#4396) ... ## Summary Multiple fixes and improvements to `spacetime dev`, `spacetime publish`, `spacetime init`, and templates: ### CLI fixes - **Fix `spacetime dev` watch path and .env.local handling** for templates with a `spacetimedb/` subdirectory - **Validate package manager availability** before installing dependencies — re-prompts if the selected PM isn't on PATH - **Remove JS/TS beta warning** from `spacetime publish` - **Remove unstable warning** from `spacetime init` - **Remove unused `spacetime energy` command** (can be re-added later when properly implemented) - **Fix `tsc` detection on Windows** — `set_extension(".cmd")` produced `tsc..cmd` (double dot); fixed to `set_extension("cmd")` - **Add `typescript` as devDependency** to all server template `spacetimedb/package.json` files so `tsc` is available during build - **Strip `\?\` extended-length path prefix** from user-facing output in both `dev` and `publish` commands (produced by `fs::canonicalize()` on Windows) - **Fix publish reporting success when user declines** non-local server prompt — changed `return Ok(())` to `bail!()` consistent with other abort cases - **Forward stdin to client process** in `spacetime dev` so interactive CLI templates work ### Template fixes - **Fix Angular template environment variables** — Angular's esbuild builder doesn't support `import.meta.env`, so we use a dev script to generate `environment.local.ts` with Angular's native `fileReplacements` pattern - **Fix TanStack Start template** — rename `createRouter` to `getRouter` (v1.121+ breaking change), upgrade to React 19, and add `@vitejs/plugin-react` for automatic JSX runtime support - **Fix `moduleResolution` in remix-ts and nextjs-ts** server tsconfigs — change from `"node"` to `"bundler"` to support subpath exports like `spacetimedb/server` - **Fix browser-ts template** — convert from static HTML + IIFE bundle to standard Vite dev server app so it works with `spacetime dev` and reads env vars from `.env.local` - **Add `deno` as devDependency** to deno-ts template (matches how bun-ts includes bun) - **Convert basic-ts from empty web app to CLI app** matching basic-rs — connect, subscribe to person table, print on insert ## Test plan - [x] `cargo test -p spacetimedb-cli` — all 133 tests pass - [ ] `spacetime dev --template angular-ts` — verify Angular app connects with correct database name - [ ] `spacetime dev --template react-ts` — verify React template still works - [ ] `spacetime dev --template tanstack-ts` — verify TanStack Start template loads without errors - [ ] `spacetime dev --template remix-ts` — verify Remix template builds and runs - [ ] `spacetime dev --template nextjs-ts` — verify Next.js template still works - [ ] `spacetime dev --template browser-ts` — verify Vite dev server starts and app connects - [ ] `spacetime dev --template bun-ts` — verify Bun CLI template runs interactively - [ ] `spacetime dev --template basic-ts` — verify CLI connects and prints on insert - [ ] Verify no `\?\` prefix in any displayed paths on Windows - [ ] Verify no `tsc not found` warning when building server modules - [ ] Select unavailable package manager at init prompt — verify re-prompt - [ ] Decline non-local server prompt — verify clean error instead of "Published successfully!" --------- Co-authored-by: Piotr Sarnacki <drogus@gmail.com> Co-authored-by: John Detter <4099508+jdetter@users.noreply.github.com> Co-authored-by: clockwork-labs-bot <bot@clockworklabs.com>	2026-02-24 02:39:42 -05:00
Piotr Sarnacki	4c962b9170	spacetime.json config implementation (#4199) ... # Description of Changes This PR implements support for the `spacetime.json` configuration file that can be used to set up common `generate` and `publish` targets. An example of `spacetime.json` could look like this: ``` { "dev_run": "pnpm dev", "generate": [ { "out-dir": "./foobar", "module-path": "region-module", "language": "c-sharp" }, { "out-dir": "./global", "module-path": "global-module", "language": "c-sharp" }, ], "publish": { "database": "bitcraft", "module-path": "spacetimedb", "server": "local", "children": [ { "database": "region-1", "module-path": "region-module", server: "local" }, { "database": "region-2", "module-path": "region-module", server: "local" } ] } } ``` With this config, running `spacetime generate` without any arguments would generate bindings for two targets: `region-module` and `global-module`. `spacetime publish` without any arguments would publish three modules, starting from the parent: `bitcraft`, `region-1`, and `region-2`. On top of that, the command `pnpm dev` would be executed when using `spacetime dev`. It is also possible to pass additional command line arguments when calling the `publish` and `generate` commands, but there are certain limitations. There is a special case when passing either a module path to generate or a module name to publish. Doing that will filter out entries in the config file that do not match. For example, running: ``` spacetime generate --project-path global-module ``` would only generate bindings for the second entry in the `generate` list. In a similar fashion, running: ``` spacetime publish region-1 ``` would only publish the child database with the name `region-1` Passing other existing arguments is also possible, but not all of the arguments are available for multiple configs. For example, when running `spacetime publish --server maincloud`, the publish command would be applied to all of the modules listed in the config file, but the `server` value from the command line arguments would take precedence. Running with arguments like `--bin-path` would, however, would throw an error as `--bin-path` makes sense only in a context of a specific module, thus this wouldn't work: `spacetime publish --bin-path spacetimedb/target/debug/bitcraft.wasm`. I will throw an error unless there is only one entry to process, thus `spacetime publish --bin-path spacetimedb/target/debug/bitcraft.wasm bitcraft` would work, as it filters the publish targets to one entry. # API and ABI breaking changes None # Expected complexity level and risk 3 The config file in itself is not overly complex, but when coupled with the CLI it is somewhat tricky to get right. There are also some changes that I had to make to how clap arguments are validated - because the values can now come from both the config file and the clap config, we can't use some of the built-in validations like `required`, or at least I haven't found a clean way to do so. # Testing I've added some automated tests, but more tests and manual testing is coming. --------- Signed-off-by: Tyler Cloutier <cloutiertyler@users.noreply.github.com> Co-authored-by: bradleyshep <148254416+bradleyshep@users.noreply.github.com> Co-authored-by: clockwork-labs-bot <clockwork-labs-bot@users.noreply.github.com> Co-authored-by: = <cloutiertyler@gmail.com> Co-authored-by: Tyler Cloutier <cloutiertyler@users.noreply.github.com>	2026-02-15 23:22:44 +00:00
clockwork-tien	99edb2954c	feat: Quickstart and client for TanStack Start (#4107) ... # Description of Changes - Quickstart template `tanstack-ts` and client for TanStack Start - Add Vue Quickstart Docs <!-- Please describe your change, mention any related tickets, and so on here. --> # Screenshots - `tanstack-ts` template <img width="1461" height="898" alt="image" src="https://github.com/user-attachments/assets/6b7e5473-33c4-4f76-92a7-18607c74422c" /> - TanStack Start Quickstart Docs <img width="1459" height="896" alt="image" src="https://github.com/user-attachments/assets/b7557498-ff5a-4ce5-9c85-68db943e1b9a" /> # API and ABI breaking changes <!-- If this is an API or ABI breaking change, please apply the corresponding GitHub label. --> # Expected complexity level and risk <!-- How complicated do you think these changes are? Grade on a scale from 1 to 5, where 1 is a trivial change, and 5 is a deep-reaching and complex change. This complexity rating applies not only to the complexity apparent in the diff, but also to its interactions with existing and future code. If you answered more than a 2, explain what is complex about the PR, and what other components it interacts with in potentially concerning ways. --> # Testing <!-- Describe any testing you've done, and any testing you'd like your reviewers to do, so that you're confident that all the changes work as expected! --> - [x] Tested the templates locally (e.g. able to add people), works well for me	2026-02-12 15:14:32 +00:00