You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
chore: keep template_api in the monorepo, drop the subtree wiring
Remove the template_api subtree recipes and their publish hooks. template_api
stays an in-repo, workspace-excluded example that still tracks the published
api version through the bump recipes.
Copy file name to clipboardExpand all lines: template_api/README.md
+2-8Lines changed: 2 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,6 @@
1
-
# nightshade-api-template
1
+
# template_api
2
2
3
-
A minimal starting point for a [nightshade-api](https://crates.io/crates/nightshade-api) program. Procedural, single file, runs natively and in the browser from the same code.
4
-
5
-
Click **Use this template** on GitHub, or clone it, to start a project.
3
+
A minimal starting point for a [nightshade-api](https://crates.io/crates/nightshade-api) program. Procedural, single file, runs natively and in the browser from the same code. Copy this directory to start a project.
`index.html` and `Trunk.toml` are the web setup: trunk compiles the crate to wasm and serves the page, which carries the `id="canvas"` the engine renders into. Keep that id.
35
33
36
34
Grow it by adding more systems to `run!` and more `spawn_` and per-frame calls. The full surface is in the [nightshade-api docs](https://docs.rs/nightshade-api).
37
-
38
-
---
39
-
40
-
This repository is synced from the [nightshade](https://github.com/matthewjberger/nightshade) monorepo, so changes land there.
0 commit comments