sitevision-cli 0.3.1-beta.2 → 0.4.0-beta.0

package/package.json

@@ -1,13 +1,13 @@
 {
 	"name": "sitevision-cli",
-	"version": "0.3.1-beta.2",
+	"version": "0.4.0-beta.0",
 	"license": "MIT",
 	"bin": {
 		"svc": "dist/cli.js"
 	},
 	"type": "module",
 	"engines": {
-		"node": ">=16"
+		"node": ">=22"
 	},
 	"scripts": {
 		"build": "tsc",
@@ -21,42 +21,35 @@
 	],
 	"dependencies": {
 		"@napi-rs/keyring": "^1.3.0",
-		"ink": "^6.6.0",
+		"ink": "^7.1.0",
 		"ink-spinner": "^5.0.0",
-		"meow": "^11.0.0",
-		"react": "^19.2.3"
+		"meow": "^14.1.0",
+		"react": "^19.2.7"
 	},
 	"devDependencies": {
-		"@sindresorhus/tsconfig": "^3.0.1",
-		"@types/node": "^25.0.3",
-		"@types/react": "^19.2.7",
+		"@eslint/compat": "^2.1.0",
+		"@sindresorhus/tsconfig": "^8.1.0",
+		"@types/node": "^26.0.0",
+		"@types/react": "^19.2.17",
 		"@vdemedes/prettier-config": "^2.0.1",
-		"ava": "^5.2.0",
-		"chalk": "^5.2.0",
-		"eslint-config-xo-react": "^0.27.0",
-		"eslint-plugin-react": "^7.32.2",
-		"eslint-plugin-react-hooks": "^4.6.0",
-		"ink-testing-library": "^3.0.0",
-		"prettier": "^2.8.7",
-		"ts-node": "^10.9.1",
-		"typescript": "^5.0.3",
-		"xo": "^0.53.1"
+		"ava": "^8.0.1",
+		"eslint-config-xo-react": "^0.30.1",
+		"eslint-plugin-react": "^7.37.5",
+		"eslint-plugin-react-hooks": "^7.1.1",
+		"ink-testing-library": "^4.0.0",
+		"prettier": "^3.8.4",
+		"tsx": "^4.22.4",
+		"typescript": "^6.0.3",
+		"xo": "^3.0.2"
 	},
 	"ava": {
-		"extensions": {
-			"ts": "module",
-			"tsx": "module"
-		},
+		"extensions": [
+			"ts",
+			"tsx"
+		],
 		"nodeArguments": [
-			"--loader=ts-node/esm"
+			"--import=tsx"
 		]
 	},
-	"xo": {
-		"extends": "xo-react",
-		"prettier": true,
-		"rules": {
-			"react/prop-types": "off"
-		}
-	},
 	"prettier": "@vdemedes/prettier-config"
 }

package/readme.md

@@ -2,6 +2,7 @@
 
 This CLI was largely built on the back of the [sitevision-scripts](https://github.com/sitevision/sitevision-scripts) project.
 However, these scripts have some limitations:
+
 - Clunky for use with environments requiring signed packages
 - Clunkly management of credentials and unsecure handling of credentials
 - No type safety
@@ -33,6 +34,7 @@ svc
 ```
 
 On first run (or if setup is incomplete), the CLI will:
+
 1. Check if `node_modules` exists and offer to run `npm install` if missing
 2. Check if dev properties are configured and offer to set them up if missing
 3. Check if you have setup signing credentials and offer to do so if missing
@@ -40,6 +42,7 @@ On first run (or if setup is incomplete), the CLI will:
 5. Show the main menu
 
 Use arrow keys to navigate and Enter to select:
+
 - **Dev** - Start development server with watch mode
 - **Dev (Signed)** - Development with automatic signing before each deploy
 - **Build** - Build a dist bundle
@@ -113,13 +116,13 @@ Create this file in your project root for deployment configuration:
 
 ```json
 {
-  "domain": "your-site.sitevision.se",
-  "siteName": "YourSite",
-  "addonName": "your-addon",
-  "username": "your-email@example.com",
-  "useHTTPForDevDeploy": false,
-  "signingUsername": "your-developer-account@example.com",
-  "certificateName": "optional-certificate-name"
+	"domain": "your-site.sitevision.se",
+	"siteName": "YourSite",
+	"addonName": "your-addon",
+	"username": "your-email@example.com",
+	"useHTTPForDevDeploy": false,
+	"signingUsername": "your-developer-account@example.com",
+	"certificateName": "optional-certificate-name"
 }
 ```
 
@@ -144,6 +147,7 @@ are never written anywhere.
 ### Signing Credentials
 
 Signing credentials are used to sign apps via developer.sitevision.se:
+
 - `signingUsername` - Your developer.sitevision.se account
 - `certificateName` - Optional, if you have multiple certificates