@todesktop/cli 1.13.0-0 → 1.14.0

package/README.md

@@ -10,7 +10,7 @@ For more information, visit the project [landing page](https://www.todesktop.com
 - [Get started](#get-started)
 - [CLI commands](#cli-commands)
 - [Automating your builds (CI)](#automating-your-builds-ci)
-- [Project configuration (todesktop.json)](#project-configuration-todesktopjson)
+- [Project configuration (todesktop.json or todesktop.js)](#project-configuration-todesktopjson-or-todesktopjs)
 - [Build lifecycle hooks (package.json scripts)](#build-lifecycle-hooks-packagejson-scripts)
 - [App package.json requirements](#app-packagejson-requirements)
 - [FAQs](#faqs)
@@ -42,14 +42,27 @@ Create a `todesktop.json` file in the root of your Electron project.
 
 ```json
 {
-  "$schema": "https://unpkg.com/@todesktop/cli@1.12.5/schemas/schema.json",
+  "$schema": "https://unpkg.com/@todesktop/cli@1.13.0/schemas/schema.json",
   "schemaVersion": 1
   "id": "your-todesktop-id",
   "icon": "./desktop-icon.png",
+  "schemaVersion": 1
 }
 ```
 
-See [Project configuration](#project-configuration-todesktopjson) for the full list of configuration options.
+Alternatively, you can create a `todesktop.js` file. This allows you to use JavaScript to dynamically generate your configuration. For example:
+
+```javascript
+const path = require("path");
+
+module.exports = {
+  id: process.env.TODESKTOP_APP_ID || "your-default-todesktop-id",
+  icon: path.join(__dirname, "assets", "desktop-icon.png"),
+  schemaVersion: 1,
+};
+```
+
+See [Project configuration](#project-configuration-todesktopjson-or-todesktopjs) for the full list of configuration options.
 
 ### Step 3: Add @todesktop/runtime as a dependency
 
@@ -135,27 +148,27 @@ This builds your Electron app with native installers, code signing, and so on ba
 We also support:
 
 - `todesktop build --code-sign=false`. Run a build with code-signing and notarization disabled. This is handy for testing builds quickly.
-- `todesktop build --config=<path.to.another.todesktop.json>`. Run a build with a different configuration file.
+- `todesktop build --config=<path.to.config.file>`. Run a build with a different configuration file (e.g., `todesktop.staging.json` or `todesktop.prod.js`).
 - `todesktop build --async`. Run a build in the background. This is handy for CI environments.
 - `todesktop build --webhook URL`. Send a POST request to the webhook URL when the build is finished. It's especially useful together with the `--async` flag.
-- `todesktop build --ignore-extends-errors`. Ignore `id` and `appId` validation errors when extending another todesktop.json file.
+- `todesktop build --ignore-extends-errors`. Ignore `id` and `appId` validation errors when extending another configuration file (`.json` or `.js`).
 - `todesktop release`. Release a build. This will publish a new download and an auto-update for existing users. By default it shows a list of builds for you to choose from.
   - Use `todesktop release <id>` to release a specific build by ID.
   - `todesktop release --latest` will release the latest build.
   - Append `--force` to skip the interactive confirmation step.
-  - Append `--config=<path.to.another.todesktop.json>` to use a different configuration file.
+  - Append `--config=<path.to.config.file>` to use a different configuration file.
 - `todesktop builds`. View your recent builds.
   - Use `todesktop builds <id>` to view a specific build and its progress.
   - `todesktop builds --latest` will show the latest build and it's progress.
   - `todesktop builds --count=<number>` will show the last `<number>` builds.
   - `todesktop builds --format=json` will output build data in JSON format.
-  - Append `--config=<path.to.another.todesktop.json>` to use a different configuration file.
+  - Append `--config=<path.to.config.file>` to use a different configuration file.
   - Append `--exit` to disable dynamic pagination and exit the process once the build data has been displayed.
 - `todesktop logout`. Logs you out.
 - `todesktop smoke-test` Check whether the build works and can be successfully updated.
   - Use `todesktop smoke-test <id>` to test a specific build by ID.
   - `todesktop smoke-test --latest` will test the latest build.
-  - Append `--config=<path.to.another.todesktop.json>` to use a different configuration file.
+  - Append `--config=<path.to.config.file>` to use a different configuration file.
 - `todesktop whoami`. Prints the email of the account you're signed into.
 - `todesktop --help`. Shows the help documentation.
 - `todesktop --version`. Shows the current version of the CLI.
@@ -207,13 +220,17 @@ The webhook receives a POST request with the following JSON body:
 }
 ```
 
-## Project configuration (todesktop.json)
+## Project configuration (todesktop.json or todesktop.js)
 
-This describes all of the possible configuration options ín your `todesktop.json`.
+This describes all of the possible configuration options in your `todesktop.json` or `todesktop.js` file.
+
+You can use a standard JSON file (`todesktop.json`) for static configuration, or a JavaScript file (`todesktop.js`) that exports a configuration object. Using a `.js` file allows for dynamic configuration, such as setting values based on environment variables or computing paths.
+
+**Note:** Schema validation and IntelliSense (described under [Installation](#installation)) currently only work for `.json` files.
 
 To avoid confusion, the following terms will be used throughout this file:
 
-- "Project root": this is the parent directory of your `todesktop.json`.
+- "Project root": this is the parent directory of your `todesktop.json` or `todesktop.js`.
 
 ### `$schema` - (optional) string
 
@@ -226,9 +243,8 @@ To enable JSON validation and IntelliSense for your `todesktop.json` file in com
 - For example, if using a hosted version of the schema:
   ```json
   {
-    "$schema": "https://unpkg.com/@todesktop/cli@1.12.5/schemas/schema.json", // Example URL
+    "$schema": "https://unpkg.com/@todesktop/cli@1.13.0/schemas/schema.json",
     "id": "your-todesktop-id"
-    // ... other configurations
   }
   ```
 - Or if ToDesktop CLI is installed locally, you can use a local path:
@@ -236,7 +252,6 @@ To enable JSON validation and IntelliSense for your `todesktop.json` file in com
   {
     "$schema": "./node_modules/@todesktop/cli/schemas/schema.json",
     "id": "your-todesktop-id"
-    // ... other configurations
   }
   ```
 
@@ -420,9 +435,11 @@ The DMG windows position and size. In most cases, you will only want to specify
 
 ### `extends` - (optional) string
 
-Example: `./todesktop.staging.json`
+Default: `null`.
 
-This is the path to a base configuration file. This is especially useful for configuration sharing between staging and production builds. The base configuration file can be a relative path from the project root or an absolute path.
+Example: `./todesktop.base.json` or `./todesktop.base.js`.
+
+This is the path to a base configuration file (`.json` or `.js`). This is especially useful for configuration sharing between different environments (e.g., staging and production). The base configuration file can be a relative path from the project root or an absolute path.
 
 For more information about how to create a staging version of your app see: [How do I create a staging version of my app?](#how-do-i-create-a-staging-version-of-my-app).
 
@@ -1204,9 +1221,9 @@ ToDesktop CLI supports the concept of a staging version of your app. This is use
 
 1. Create a new app in ToDesktop's web UI.
 
-2. Create a new todesktop configuration file named `todesktop.staging.json`
+2. Create a new configuration file, for example `todesktop.staging.json` or `todesktop.staging.js`.
 
-3. Add the following to your `todesktop.staging.json` file:
+3. Add the following to your staging configuration file (e.g., `todesktop.staging.json`):
 
 ```json
 {
@@ -1288,6 +1305,17 @@ Now, when we build your app on ToDesktop servers, it will also run your custom `
 
 ## Changelog
 
+### v1.14.0
+
+- Add support for `todesktop.js` configuration file for dynamic configurations.
+- Upgrade to Firebase v11.
+- Update Node.js engine requirement from >=12 to >=16.
+
+### v1.13.0
+
+- Add support for `platformOverrides` in config to specify platform-specific overrides for app configuration
+- Add support for `$schema` in config to enable JSON schema validation and IDE intellisense
+
 ### v1.12.5
 
 - Fix: Removed invalid React Hook call in `BuildCommand` that caused errors.
@@ -1395,7 +1423,7 @@ Now, when we build your app on ToDesktop servers, it will also run your custom `
 
 ### v1.9.0
 
-- You can now specify `@electron/rebuild` as a custom `rebuildLibrary` in your `todesktop.json` file.
+- You can now specify `@electron/rebuild` as a custom `rebuildLibrary` in your configuration file.
 
 ### v1.8.1
 
@@ -1405,8 +1433,8 @@ Now, when we build your app on ToDesktop servers, it will also run your custom `
 
 - Add support for `--webhook` flag for `todesktop build` command
 - Add support for `--async` flag to run a build in the in the background
-- Add support for specifying custom `yarnVersion` in config
-- Add support for specifying custom `pnpmVersion` in config
+- Add support for specifying custom `yarnVersion` in the configuration file
+- Add support for specifying custom `pnpmVersion` in the configuration file
 
 ### v1.7.7
 
@@ -1418,8 +1446,8 @@ Now, when we build your app on ToDesktop servers, it will also run your custom `
 
 ### v1.7.5
 
-- Add support for specifying custom `npmVersion` in config
-- Add support for bundling a requirements file for Mac
+- Add support for specifying custom `npmVersion` in the configuration file
+- Add support for bundling a requirements file for Mac (`mac.requirements`)
 
 ### v1.7.4
 
@@ -1431,7 +1459,7 @@ Now, when we build your app on ToDesktop servers, it will also run your custom `
 
 ### v1.7.1
 
-- Add support for specifying custom `appBuilderLibVersion` in config
+- Add support for specifying custom `appBuilderLibVersion` in the configuration file
 - Show suggestion to run a Smoke Test when releasing an untested build
 
 ### v1.7.0
@@ -1440,15 +1468,15 @@ Now, when we build your app on ToDesktop servers, it will also run your custom `
 
 ### v1.6.3
 
-- Add support for specifying custom `windows.nsisCustomBinary` in config
+- Add support for specifying custom `windows.nsisCustomBinary` in the configuration file
 
 ### v1.6.2
 
-- Add support for specifying custom `nodeVersion` in config
+- Add support for specifying custom `nodeVersion` in the configuration file
 
 ### v1.6.1
 
-- Add support for specifying `windows.nsisInclude` in config
+- Add support for specifying `windows.nsisInclude` in the configuration file
 
 ### v1.6.0
 
@@ -1477,7 +1505,7 @@ Now, when we build your app on ToDesktop servers, it will also run your custom `
 
 ### v1.4.0
 
-- Adds `extends` and `packageJson` field to `todesktop.json` file.
+- Adds `extends` and `packageJson` fields to the configuration file.
 - Added `--config` option to pass a different configuration file.
 
 ### v1.3.0