This repository was archived by the owner on Nov 9, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 24
This repository was archived by the owner on Nov 9, 2023. It is now read-only.
UnhandledPromiseRejectionWarning: Unhandled promise rejection #33
Copy link
Copy link
Open
Description
Describe the bug
A clear and concise description of what the bug is.
Upon creating a new project, got the following at the end of tauri:build:
Bundling "/Volumes/MacHD2/apps/app-tauri-first/src-tauri/target/release/bundle/dmg/App First_0.1.0_x64.dmg"
info: running bundle_dmg.sh
Error: failed to bundle project
Caused by:
Shell Scripting Error:`error running bundle_dmg.sh, try running with --verbose to see command output`
app:spawn Command "/Volumes/MacHD2/apps/app-tauri-first/node_modules/@tauri-apps/cli/bin/tauri-cli" failed with exit code: 1 +0ms
(node:65482) UnhandledPromiseRejectionWarning: Error
at d (/Volumes/MacHD2/apps/app-tauri-first/node_modules/@tauri-apps/cli/dist/api/cli.js:1:9485)
at v (/Volumes/MacHD2/apps/app-tauri-first/node_modules/@tauri-apps/cli/dist/api/cli.js:1:9526)
at ChildProcess.<anonymous> (/Volumes/MacHD2/apps/app-tauri-first/node_modules/@tauri-apps/cli/dist/api/cli.js:1:10657)
at ChildProcess.emit (events.js:376:20)
at maybeClose (internal/child_process.js:1055:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:288:5)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:65482) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:65482) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
To Reproduce
Steps to reproduce the behavior:
vue create my-new-tauri-app
cd my-new-tauri-app
vue add tauri
yarn tauri:serve
then
yarn tauri:build
Environment (please complete the following information):
-
vue-cli-plugin-tauri version : 1.0.0-beta.2
-
other vue plugins used:
-
- "@vue/cli-plugin-babel": "~4.5.0",
-
- "@vue/cli-plugin-eslint": "~4.5.0",
-
- "@vue/cli-plugin-pwa": "~4.5.0",
-
- "@vue/cli-plugin-router": "~4.5.0",
-
- "@vue/cli-plugin-vuex": "~4.5.0",
-
- "@vue/cli-service": "~4.5.0",
-
- "@vue/compiler-sfc": "^3.0.0",
-
output from
npx tauri info/yarn tauri info:
Operating System - Mac OS, version 10.14.6 X64
Node.js environment
Node.js - 14.17.0
@tauri-apps/cli - 1.0.0-beta.1
@tauri-apps/api - Not installed
Global packages
npm - 6.14.13
yarn - 1.22.10
Rust environment
rustc - 1.52.1
cargo - 1.52.0
App directory structure
/.git
/node_modules
/public
/src
/src-tauri
App
tauri.rs - 1.0.0-beta.1
build-type - bundle
CSP - default-src blob: data: filesystem: ws: http: https: 'unsafe-eval' 'unsafe-inline' 'self' img-src: 'self'
distDir - Set automatically by Vue CLI plugin
devPath - Set automatically by Vue CLI plugin
framework - Vue.js (Vue CLI)
bundler - Webpack
Additional context
There may not be an issue in the actual app that is built. Would be more confident if it didn't have errors. I do not know exactly how to hunt the issue down myself.
Metadata
Metadata
Assignees
Labels
No labels