napi-rs/examples/napi/electron-renderer/index.js

const { ipcRenderer } = require('electron')

const { callLongThreadsafeFunction } = require('../index.cjs')

callLongThreadsafeFunction(() => {})

ipcRenderer.on('ping', () => ipcRenderer.send('pong'))
fix(napi): check if the tokio runtime exists when registering the module And recreate it if it does not exist. In windows, electron renderer process will crash if: 1. Import some NAPI module that enable `tokio-rt` flag in renderer process. 2. Reload the page. 3. Call a function imported from that NAPI module. Because the tokio runtime will be dropped when reloading the page, and won't create again, but currently we assume that the runtime must exist in tokio-based `within_runtime_if_available`. This will cause some panic like this: ``` thread '<unnamed>' panicked at 'called `Option::unwrap()` on a `None` value', napi-rs\crates\napi\src\tokio_runtime.rs:72:42 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace Error: Renderer process crashed: crashed, exitCode: -529697949 at EventEmitter.<anonymous> (napi-rs\examples\napi\electron.js:33:9) at EventEmitter.emit (node:events:525:35) ``` 2023-03-28 13:03:00 +09:00			`const { ipcRenderer } = require('electron')`

refactor(cli): refactor js-binding to support easier bundling. (#1957) * Refactor js-binding to support bundling single-package artifacts The existsSync check breaks the bundlers I've tested (esbuild, webpack, ncc), so you cannot bundle napi-rs packages that have all binarys in a single package. I've tested this change with both single package and multi package libraries. * Update snapshots * Update CI * Fix electron test --------- Co-authored-by: Caleb ツ Everett <calebev@amazon.com> Co-authored-by: LongYinan <lynweklm@gmail.com> 2024-02-26 16:46:07 +09:00			`const { callLongThreadsafeFunction } = require('../index.cjs')`
fix(napi): check if the tokio runtime exists when registering the module And recreate it if it does not exist. In windows, electron renderer process will crash if: 1. Import some NAPI module that enable `tokio-rt` flag in renderer process. 2. Reload the page. 3. Call a function imported from that NAPI module. Because the tokio runtime will be dropped when reloading the page, and won't create again, but currently we assume that the runtime must exist in tokio-based `within_runtime_if_available`. This will cause some panic like this: ``` thread '<unnamed>' panicked at 'called `Option::unwrap()` on a `None` value', napi-rs\crates\napi\src\tokio_runtime.rs:72:42 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace Error: Renderer process crashed: crashed, exitCode: -529697949 at EventEmitter.<anonymous> (napi-rs\examples\napi\electron.js:33:9) at EventEmitter.emit (node:events:525:35) ``` 2023-03-28 13:03:00 +09:00
test(napi): update test case for checking electron renderer crash (#1547) (cherry picked from commit d22598dbb1082de8ac712de954cd5616c838a48d) 2023-03-29 13:53:57 +09:00			`callLongThreadsafeFunction(() => {})`
fix(napi): check if the tokio runtime exists when registering the module And recreate it if it does not exist. In windows, electron renderer process will crash if: 1. Import some NAPI module that enable `tokio-rt` flag in renderer process. 2. Reload the page. 3. Call a function imported from that NAPI module. Because the tokio runtime will be dropped when reloading the page, and won't create again, but currently we assume that the runtime must exist in tokio-based `within_runtime_if_available`. This will cause some panic like this: ``` thread '<unnamed>' panicked at 'called `Option::unwrap()` on a `None` value', napi-rs\crates\napi\src\tokio_runtime.rs:72:42 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace Error: Renderer process crashed: crashed, exitCode: -529697949 at EventEmitter.<anonymous> (napi-rs\examples\napi\electron.js:33:9) at EventEmitter.emit (node:events:525:35) ``` 2023-03-28 13:03:00 +09:00
			`ipcRenderer.on('ping', () => ipcRenderer.send('pong'))`