@tauri-apps/cli 2.0.0-beta.0 → 2.0.0-beta.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +11 -0
- package/main.js +3 -3
- package/package.json +11 -11
- package/schema.json +1 -1
- package/src/lib.rs +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,16 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## \[2.0.0-beta.1]
|
|
4
|
+
|
|
5
|
+
### Enhancements
|
|
6
|
+
|
|
7
|
+
- [`4e101f80`](https://www.github.com/tauri-apps/tauri/commit/4e101f801657e7d01ce8c22f9c6468067d0caab2)([#8756](https://www.github.com/tauri-apps/tauri/pull/8756)) Moved the capability JSON schema to the `src-tauri/gen` folder so it's easier to track changes on the `capabilities` folder.
|
|
8
|
+
- [`4e101f80`](https://www.github.com/tauri-apps/tauri/commit/4e101f801657e7d01ce8c22f9c6468067d0caab2)([#8756](https://www.github.com/tauri-apps/tauri/pull/8756)) Update app and plugin templates following generated files change from tauri-build and tauri-plugin.
|
|
9
|
+
|
|
10
|
+
### Dependencies
|
|
11
|
+
|
|
12
|
+
- Upgraded to `tauri-cli@2.0.0-beta.1`
|
|
13
|
+
|
|
3
14
|
## \[2.0.0-beta.0]
|
|
4
15
|
|
|
5
16
|
### New Features
|
package/main.js
CHANGED
|
@@ -6,9 +6,9 @@ const { run, logError } = require('./index')
|
|
|
6
6
|
|
|
7
7
|
module.exports.run = (args, binName) => {
|
|
8
8
|
return new Promise((resolve, reject) => {
|
|
9
|
-
run(args, binName, res => {
|
|
10
|
-
if (
|
|
11
|
-
reject(
|
|
9
|
+
run(args, binName, (error, res) => {
|
|
10
|
+
if (error) {
|
|
11
|
+
reject(error)
|
|
12
12
|
} else {
|
|
13
13
|
resolve(res)
|
|
14
14
|
}
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@tauri-apps/cli",
|
|
3
|
-
"version": "2.0.0-beta.
|
|
3
|
+
"version": "2.0.0-beta.1",
|
|
4
4
|
"description": "Command line interface for building Tauri apps",
|
|
5
5
|
"funding": {
|
|
6
6
|
"type": "opencollective",
|
|
@@ -68,15 +68,15 @@
|
|
|
68
68
|
"format:check": "prettier --check ./package.json ./tauri.js"
|
|
69
69
|
},
|
|
70
70
|
"optionalDependencies": {
|
|
71
|
-
"@tauri-apps/cli-win32-x64-msvc": "2.0.0-beta.
|
|
72
|
-
"@tauri-apps/cli-darwin-x64": "2.0.0-beta.
|
|
73
|
-
"@tauri-apps/cli-linux-x64-gnu": "2.0.0-beta.
|
|
74
|
-
"@tauri-apps/cli-darwin-arm64": "2.0.0-beta.
|
|
75
|
-
"@tauri-apps/cli-linux-arm64-gnu": "2.0.0-beta.
|
|
76
|
-
"@tauri-apps/cli-linux-arm64-musl": "2.0.0-beta.
|
|
77
|
-
"@tauri-apps/cli-linux-arm-gnueabihf": "2.0.0-beta.
|
|
78
|
-
"@tauri-apps/cli-linux-x64-musl": "2.0.0-beta.
|
|
79
|
-
"@tauri-apps/cli-win32-ia32-msvc": "2.0.0-beta.
|
|
80
|
-
"@tauri-apps/cli-win32-arm64-msvc": "2.0.0-beta.
|
|
71
|
+
"@tauri-apps/cli-win32-x64-msvc": "2.0.0-beta.1",
|
|
72
|
+
"@tauri-apps/cli-darwin-x64": "2.0.0-beta.1",
|
|
73
|
+
"@tauri-apps/cli-linux-x64-gnu": "2.0.0-beta.1",
|
|
74
|
+
"@tauri-apps/cli-darwin-arm64": "2.0.0-beta.1",
|
|
75
|
+
"@tauri-apps/cli-linux-arm64-gnu": "2.0.0-beta.1",
|
|
76
|
+
"@tauri-apps/cli-linux-arm64-musl": "2.0.0-beta.1",
|
|
77
|
+
"@tauri-apps/cli-linux-arm-gnueabihf": "2.0.0-beta.1",
|
|
78
|
+
"@tauri-apps/cli-linux-x64-musl": "2.0.0-beta.1",
|
|
79
|
+
"@tauri-apps/cli-win32-ia32-msvc": "2.0.0-beta.1",
|
|
80
|
+
"@tauri-apps/cli-win32-arm64-msvc": "2.0.0-beta.1"
|
|
81
81
|
}
|
|
82
82
|
}
|
package/schema.json
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"$schema": "http://json-schema.org/draft-07/schema#",
|
|
3
3
|
"title": "Config",
|
|
4
|
-
"description": "The Tauri configuration object. It is read from a file where you can define your frontend assets, configure the bundler and define a tray icon.\n\nThe configuration file is generated by the [`tauri init`](https://tauri.app/v1/api/cli#init) command that lives in your Tauri application source directory (src-tauri).\n\nOnce generated, you may modify it at will to customize your Tauri application.\n\n## File Formats\n\nBy default, the configuration is defined as a JSON file named `tauri.conf.json`.\n\nTauri also supports JSON5 and TOML files via the `config-json5` and `config-toml` Cargo features, respectively. The JSON5 file name must be either `tauri.conf.json` or `tauri.conf.json5`. The TOML file name is `Tauri.toml`.\n\n## Platform-Specific Configuration\n\nIn addition to the default configuration file, Tauri can read a platform-specific configuration from `tauri.linux.conf.json`, `tauri.windows.conf.json`, `tauri.macos.conf.json`, `tauri.android.conf.json` and `tauri.ios.conf.json` (or `Tauri.linux.toml`, `Tauri.windows.toml`, `Tauri.macos.toml`, `Tauri.android.toml` and `Tauri.ios.toml` if the `Tauri.toml` format is used), which gets merged with the main configuration object.\n\n## Configuration Structure\n\nThe configuration is composed of the following objects:\n\n- [`
|
|
4
|
+
"description": "The Tauri configuration object. It is read from a file where you can define your frontend assets, configure the bundler and define a tray icon.\n\nThe configuration file is generated by the [`tauri init`](https://tauri.app/v1/api/cli#init) command that lives in your Tauri application source directory (src-tauri).\n\nOnce generated, you may modify it at will to customize your Tauri application.\n\n## File Formats\n\nBy default, the configuration is defined as a JSON file named `tauri.conf.json`.\n\nTauri also supports JSON5 and TOML files via the `config-json5` and `config-toml` Cargo features, respectively. The JSON5 file name must be either `tauri.conf.json` or `tauri.conf.json5`. The TOML file name is `Tauri.toml`.\n\n## Platform-Specific Configuration\n\nIn addition to the default configuration file, Tauri can read a platform-specific configuration from `tauri.linux.conf.json`, `tauri.windows.conf.json`, `tauri.macos.conf.json`, `tauri.android.conf.json` and `tauri.ios.conf.json` (or `Tauri.linux.toml`, `Tauri.windows.toml`, `Tauri.macos.toml`, `Tauri.android.toml` and `Tauri.ios.toml` if the `Tauri.toml` format is used), which gets merged with the main configuration object.\n\n## Configuration Structure\n\nThe configuration is composed of the following objects:\n\n- [`app`](#appconfig): The Tauri configuration - [`build`](#buildconfig): The build configuration - [`bundle`](#bundleconfig): The bundle configurations - [`plugins`](#pluginconfig): The plugins configuration\n\n```json title=\"Example tauri.config.json file\" { \"productName\": \"tauri-app\", \"version\": \"0.1.0\" \"build\": { \"beforeBuildCommand\": \"\", \"beforeDevCommand\": \"\", \"devUrl\": \"../dist\", \"frontendDist\": \"../dist\" }, \"app\": { \"security\": { \"csp\": null }, \"windows\": [ { \"fullscreen\": false, \"height\": 600, \"resizable\": true, \"title\": \"Tauri App\", \"width\": 800 } ] }, \"bundle\": {}, \"plugins\": {} } ```",
|
|
5
5
|
"type": "object",
|
|
6
6
|
"properties": {
|
|
7
7
|
"$schema": {
|
package/src/lib.rs
CHANGED
|
@@ -12,7 +12,7 @@ pub fn run(args: Vec<String>, bin_name: Option<String>, callback: JsFunction) ->
|
|
|
12
12
|
let function: ThreadsafeFunction<bool, ErrorStrategy::CalleeHandled> = callback
|
|
13
13
|
.create_threadsafe_function(0, |ctx| ctx.env.get_boolean(ctx.value).map(|v| vec![v]))?;
|
|
14
14
|
|
|
15
|
-
// we need to run in a separate thread so Node.js
|
|
15
|
+
// we need to run in a separate thread so Node.js consumers
|
|
16
16
|
// can do work while `tauri dev` is running.
|
|
17
17
|
std::thread::spawn(move || match tauri_cli::try_run(args, bin_name) {
|
|
18
18
|
Ok(_) => function.call(Ok(true), ThreadsafeFunctionCallMode::Blocking),
|