dewctl 0.5.2 → 0.5.4

package/README.md

@@ -3,24 +3,8 @@
 The Dewdrop CLI builds your three.js game, uploads it to Dewdrop as you work,
 and publishes it for players.
 
-## Start a game
-
-In a new, empty folder, with Node.js 24 or newer:
-
-```sh
-npx dewctl init
-npm install
-npx dewctl login
-npx dewctl dev --watch
-```
-
-`dev --watch` prints a link to play your game and uploads it again each time
-you save. When it's ready, `npx dewctl publish` puts it in front of players.
-
-## Docs
-
-The development flow, every command, `dewdrop.json` and troubleshooting are in
-the docs: https://alpha.dewdrop.world/docs
+Getting started, every command, `dewdrop.json` and troubleshooting are in the
+docs: https://alpha.dewdrop.world/docs
 
 ## License
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dewctl",
-  "version": "0.5.2",
+  "version": "0.5.4",
   "description": "Build and publish three.js games on Dewdrop.",
   "license": "MIT",
   "type": "module",

package/src/project.js

@@ -157,8 +157,9 @@ export async function build(project, signal) {
 // starter game, depending on the SDK and this CLI from npm; one holding any of them has a game of its own and gets
 // dewdrop.json alone, so nothing of it is touched and no starter is left half written.
 const STARTER_FILES=['package.json','src','index.html','vite.config.js'];
-// The SDK a new game depends on, and this CLI, at its own version.
-const SDK_RANGE='^0.4.0';
+// The SDK a new game depends on — the range moves with the SDK's minor, since a caret on 0.x stays within one —
+// and this CLI, at its own version.
+const SDK_RANGE='^0.5.1';
 const CLI_RANGE=`^${JSON.parse(readFileSync(new URL('../package.json',import.meta.url),'utf8')).version}`;
 // A game name from the project directory, or a random one when the directory name yields nothing usable.
 function gameNameFrom(root) {