windows compatibility improvements

Author: marcomq

Cargo.toml

@@ -15,18 +15,19 @@ repository = "https://github.com/marcomq/tauri-plugin-deno"
 tauri = { version = "2" }
 serde = "1.0"
 thiserror = "2"
-
 deno_core = "0.338"
 deno_fs = "0.103.0"
 deno_error = "0.5.5"
-deno_runtime = { version = "0.201", features = ["transpile"] } # , features = ["include_js_files_for_snapshotting"] }
+deno_runtime = { version = "0.201", features = ["transpile"] } 
 deno_resolver = "0.24.0"
 sys_traits = "0.1.8"
-
 reqwest = "0.12"
 tokio = { version = "1.43.0", features = ["full"] }
 lazy_static = "1.5.0"
-# deno_runtime = { version = "0.201" } # , features = ["include_js_files_for_snapshotting"] }
 
 [build-dependencies]
 tauri-plugin = { version = "2", features = ["build"] }
+
+
+[target.'cfg(windows)'.dependencies]
+winapi = { version = "0.3.9", features = ["sysinfoapi"] }

README.md

@@ -13,7 +13,7 @@ The source files are expected to be in `src-tauri/src-deno`. Changing them will
 
 ## Status
 
-This plugin was currently only tested it on MacOS.
+This plugin was tested on MacOS & Windows and is expected to work fine on linux too. There still seem to be issues on windows production binaries, as Deno code isn't called on windows.
 
 Current TODO list:
 - make sure that windows & linux production binaries are working fine
@@ -78,4 +78,10 @@ There are following additional permissions available that can be added to by usi
 - allow-call-function (allows `callFunction`; calls function in backend; enabled by default)
 - allow-read-variable (allows `readVariable`; read js variable from backend)
 - allow-register-function (allows `registerFunction`; client side way of allowing additional functions)
-- allow-run-code  (allows `runCode`; call code directly in backend)
+- allow-run-code  (allows `runCode`; call code directly in backend)
+
+## Preconditions:
+In addition to the usual tauri preconditions, like installing rust, you need to perform following steps:
+
+Windows: 
+- install clang/llvm: `choco install llvm`

build.rs

@@ -16,4 +16,4 @@ fn main() {
         .android_path("android")
         .ios_path("ios")
         .build();
-}
+}

examples/tauri-app/package.json

@@ -4,8 +4,9 @@
   "version": "0.3.0",
   "type": "module",
   "scripts": {
-    "pretauri": "deno run --allow-read --allow-write --allow-env --allow-net --allow-run npm:tauri-plugin-deno-api src-tauri/src-deno/main.js &",
-    "tauri": "tauri"
+    "deno:bundle_and_tauri": "deno run --allow-read --allow-write --allow-env --allow-net --allow-run npm:tauri-plugin-deno-api src-tauri/src-deno/main.js & tauri",
+    "npm:tauri": "tauri",
+    "tauri": "deno task deno:bundle_and_tauri"
   },
   "dependencies": {
     "@tauri-apps/api": "^2.3",

examples/tauri-app/src-tauri/gen/schemas/desktop-schema.json

@@ -37,7 +37,7 @@
   ],
   "definitions": {
     "Capability": {
-      "description": "A grouping and boundary mechanism developers can use to isolate access to the IPC layer.\n\nIt controls application windows fine grained access to the Tauri core, application, or plugin commands. If a window is not matching any capability then it has no access to the IPC layer at all.\n\nThis can be done to create groups of windows, based on their required system access, which can reduce impact of frontend vulnerabilities in less privileged windows. Windows can be added to a capability by exact name (e.g. `main-window`) or glob patterns like `*` or `admin-*`. A Window can have none, one, or multiple associated capabilities.\n\n## Example\n\n```json { \"identifier\": \"main-user-files-write\", \"description\": \"This capability allows the `main` window on macOS and Windows access to `filesystem` write related commands and `dialog` commands to enable programatic access to files selected by the user.\", \"windows\": [ \"main\" ], \"permissions\": [ \"core:default\", \"dialog:open\", { \"identifier\": \"fs:allow-write-text-file\", \"allow\": [{ \"path\": \"$HOME/test.txt\" }] }, ], \"platforms\": [\"macOS\",\"windows\"] } ```",
+      "description": "A grouping and boundary mechanism developers can use to isolate access to the IPC layer.\n\nIt controls application windows' and webviews' fine grained access to the Tauri core, application, or plugin commands. If a webview or its window is not matching any capability then it has no access to the IPC layer at all.\n\nThis can be done to create groups of windows, based on their required system access, which can reduce impact of frontend vulnerabilities in less privileged windows. Windows can be added to a capability by exact name (e.g. `main-window`) or glob patterns like `*` or `admin-*`. A Window can have none, one, or multiple associated capabilities.\n\n## Example\n\n```json { \"identifier\": \"main-user-files-write\", \"description\": \"This capability allows the `main` window on macOS and Windows access to `filesystem` write related commands and `dialog` commands to enable programatic access to files selected by the user.\", \"windows\": [ \"main\" ], \"permissions\": [ \"core:default\", \"dialog:open\", { \"identifier\": \"fs:allow-write-text-file\", \"allow\": [{ \"path\": \"$HOME/test.txt\" }] }, ], \"platforms\": [\"macOS\",\"windows\"] } ```",
       "type": "object",
       "required": [
         "identifier",
@@ -70,14 +70,14 @@
           "type": "boolean"
         },
         "windows": {
-          "description": "List of windows that are affected by this capability. Can be a glob pattern.\n\nOn multiwebview windows, prefer [`Self::webviews`] for a fine grained access control.\n\n## Example\n\n`[\"main\"]`",
+          "description": "List of windows that are affected by this capability. Can be a glob pattern.\n\nIf a window label matches any of the patterns in this list, the capability will be enabled on all the webviews of that window, regardless of the value of [`Self::webviews`].\n\nOn multiwebview windows, prefer specifying [`Self::webviews`] and omitting [`Self::windows`] for a fine grained access control.\n\n## Example\n\n`[\"main\"]`",
           "type": "array",
           "items": {
             "type": "string"
           }
         },
         "webviews": {
-          "description": "List of webviews that are affected by this capability. Can be a glob pattern.\n\nThis is only required when using on multiwebview contexts, by default all child webviews of a window that matches [`Self::windows`] are linked.\n\n## Example\n\n`[\"sub-webview-one\", \"sub-webview-two\"]`",
+          "description": "List of webviews that are affected by this capability. Can be a glob pattern.\n\nThe capability will be enabled on all the webviews whose label matches any of the patterns in this list, regardless of whether the webview's window label matches a pattern in [`Self::windows`].\n\n## Example\n\n`[\"sub-webview-one\", \"sub-webview-two\"]`",
           "type": "array",
           "items": {
             "type": "string"
@@ -201,11 +201,26 @@
           "type": "string",
           "const": "core:app:allow-default-window-icon"
         },
+        {
+          "description": "Enables the fetch_data_store_identifiers command without any pre-configured scope.",
+          "type": "string",
+          "const": "core:app:allow-fetch-data-store-identifiers"
+        },
+        {
+          "description": "Enables the identifier command without any pre-configured scope.",
+          "type": "string",
+          "const": "core:app:allow-identifier"
+        },
         {
           "description": "Enables the name command without any pre-configured scope.",
           "type": "string",
           "const": "core:app:allow-name"
         },
+        {
+          "description": "Enables the remove_data_store command without any pre-configured scope.",
+          "type": "string",
+          "const": "core:app:allow-remove-data-store"
+        },
         {
           "description": "Enables the set_app_theme command without any pre-configured scope.",
           "type": "string",
@@ -236,11 +251,26 @@
           "type": "string",
           "const": "core:app:deny-default-window-icon"
         },
+        {
+          "description": "Denies the fetch_data_store_identifiers command without any pre-configured scope.",
+          "type": "string",
+          "const": "core:app:deny-fetch-data-store-identifiers"
+        },
+        {
+          "description": "Denies the identifier command without any pre-configured scope.",
+          "type": "string",
+          "const": "core:app:deny-identifier"
+        },
         {
           "description": "Denies the name command without any pre-configured scope.",
           "type": "string",
           "const": "core:app:deny-name"
         },
+        {
+          "description": "Denies the remove_data_store command without any pre-configured scope.",
+          "type": "string",
+          "const": "core:app:deny-remove-data-store"
+        },
         {
           "description": "Denies the set_app_theme command without any pre-configured scope.",
           "type": "string",
@@ -1036,6 +1066,11 @@
           "type": "string",
           "const": "core:window:allow-internal-toggle-maximize"
         },
+        {
+          "description": "Enables the is_always_on_top command without any pre-configured scope.",
+          "type": "string",
+          "const": "core:window:allow-is-always-on-top"
+        },
         {
           "description": "Enables the is_closable command without any pre-configured scope.",
           "type": "string",
@@ -1401,6 +1436,11 @@
           "type": "string",
           "const": "core:window:deny-internal-toggle-maximize"
         },
+        {
+          "description": "Denies the is_always_on_top command without any pre-configured scope.",
+          "type": "string",
+          "const": "core:window:deny-is-always-on-top"
+        },
         {
           "description": "Denies the is_closable command without any pre-configured scope.",
           "type": "string",