napi-rs/examples/napi/tsconfig.json

{
  "extends": "../tsconfig.json",
  "include": ["."],
  "compilerOptions": {
    "outDir": "./dist",
    "rootDir": "__test__",
    "target": "ES2018",
    "skipLibCheck": false
  },
  "exclude": ["dist", "electron.js", "electron-renderer"]
}
build: fix ts file build 2020-08-24 18:06:26 +09:00			`{`
			`"extends": "../tsconfig.json",`
			`"include": ["."],`
			`"compilerOptions": {`
chore: ts project configuration fix for test_module 2020-12-10 15:05:00 +09:00			`"outDir": "./dist",`
ci: add musl-cross toolchains into alpine.Dockerfile 2021-07-22 00:46:45 +09:00			`"rootDir": "__test__",`
fix(napi-derive): invalid TypeScript return type 2022-04-27 19:19:38 +09:00			`"target": "ES2018",`
			`"skipLibCheck": false`
chore: upgrade deps and fix type-check error 2020-08-24 19:01:55 +09:00			`},`
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			`"exclude": ["dist", "electron.js", "electron-renderer"]`
build: fix ts file build 2020-08-24 18:06:26 +09:00			`}`