naskya/napi-rs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
2572 commits 1 branch 0 tags 24 MiB
Commit graph

376 commits

Author SHA1 Message Date
LongYinan
33cf208758
Release independent packages 
napi@2.15.4
 2024-02-22 19:01:18 +08:00
Tom Barham
ebd5eef267
fix(napi): require static lifetime on add_finalizer callback (#1968) 
Co-authored-by: LongYinan <lynweklm@gmail.com>
 2024-02-22 18:40:04 +08:00
Louis
5b5f616d81
fix(napi): no hard fail on ThreadsafeFunction::call_async (#1970) 
For many reasons, in an app we can end up in a scenario where the thread / task that initially called the ThreadsafeFunction gets interrupted. This means that the receiver would get collected, should a ThreadsafeFunction be awaited on the said thread. This will create an error when the ThreadsafeFunction's callback will be called, and call a napi_fatal_error.

This change makes it so that if the send errors, this error is hidden and thus prevents any hard failure. If a ThreadsafeFunction is called in such a case, its output won't be used, but we'll still run all the logic to ensure it ran properly.

Fixes https://github.com/napi-rs/napi-rs/issues/1665 - cc @Brooooooklyn
 2024-02-22 17:34:10 +08:00
LongYinan
8855f18f50
Release independent packages 
napi@2.15.3
 2024-02-21 23:16:27 +08:00
Louis
9391196eef
fix(napi): prevent memory leak when Custom GC is used (#1963) 
There is a piece of custom logic that has been added a while back to ensure
that Buffers can be sent across threads, and be dropped properly. This involves
a custom GC that runs on NodeJS's current thread (per my understanding). The
logic to drop the buffer on that custom GC differed from the one in the Drop
impl. This meant that everytime Node sent a buffer back to a napi-rs function,
the reference wouldn't be cleaned up properly, and it would leak (96 bytes per
Reference on an ARM MacOS machine).

This commit updates the logic in the custom GC so that it matches the one in
the Drop impl. This worked locally, and fixed any occurence of the leak I could
find.
 2024-02-20 20:36:21 +08:00
Louis
90e3a349db
fix: remove outdated rustdoc about tokio channels (#1961) 
This seems to be a relic of when napi-rs used channels to send data to the
tokio runtime. This removes the outdated doc, as this could be misleading if
one wants to understand what those channels are about.
 2024-02-20 16:36:29 +08:00
LongYinan
97039b2f08
Release independent packages 
- napi@2.15.2
- napi-derive@2.15.2
 2024-02-17 22:58:31 +08:00
LongYinan
c49309fdc2
fix(napi): memory leak while using Reference (#1954) 
- Close https://github.com/napi-rs/napi-rs/issues/1952
 2024-02-17 22:14:27 +08:00
LongYinan
5ac153388f
feat(napi): accept slice as TypedArray (#1951) 2024-02-15 23:40:45 +08:00
LongYinan
d7dc4dc5a2
feat(napi): extends the Map types interoperability (#1950) 2024-02-15 15:43:21 +08:00
LongYinan
5b66467e09
Release independent packages 
- napi@2.15.1
 2024-02-01 22:16:22 +08:00
jkomyno
a5f3b2e78c fix(napi): in "Object::get", return null values wrapped in a "Some" 2024-01-31 15:50:58 +01:00
Janrupf
ac3626a023
fix(napi): Fix buffer corruption and soundness issues (#1923) 
* fix(napi): Fix buffer corruption and soundness issues

* test: fix tests to conform to buffer API
 2024-01-29 18:32:28 +08:00
LongYinan
a6aaa94e7d
Release independent packages 
- napi@2.15.0
- napi-derive@2.15.0
 2024-01-26 14:32:24 +08:00
LongYinan
f625328868
fix(napi): move JsValuesTupleIntoVec trait to function.rs 2024-01-26 14:32:24 +08:00
LongYinan
f69771e2d4
fix(napi-derive): JsArrayBuffer generated type 2024-01-26 14:32:24 +08:00
LongYinan
b9ba7c9d68
fix(napi): memory issue while creating external buffer on electron 2024-01-26 14:32:24 +08:00
LongYinan
aff95d0271
chore(napi): remove napi_val on Ref because it is unused 2024-01-26 03:29:52 +00:00
LongYinan
12503a8061
chore(napi): delete unwrap_from_ref API because it was never work 2024-01-26 02:58:53 +00:00
LongYinan
fecd0d8049
Update crates/napi/src/bindgen_runtime/js_values/function.rs 2024-01-26 02:27:46 +00:00
LongYinan
5be7ab0f6b
feat(napi): new Function/FunctionRef API 2024-01-26 02:27:46 +00:00
LongYinan
134707ef1d
fix(napi): callback in execute_tokio_future does not need to be Send (#1917) 
The resolver does not need to be `Send` or `Sync`, because it's assumed to be called from the same thread that the JavaScript thread is running on.
 2024-01-26 10:27:17 +08:00
LongYinan
69d2a75384
Release independent packages 
- napi@2.14.4
 2024-01-24 17:20:46 +08:00
LongYinan
e332270698
fix(napi): future in block_on do not need to be send 2024-01-24 17:20:31 +08:00
LongYinan
3cbae4e8c1
Release independent packages 
- napi@2.14.3
 2024-01-24 17:16:41 +08:00
LongYinan
38568c2693
chore(napi): expose spawn_blocking on tokio runtime (#1912) 2024-01-24 17:15:36 +08:00
LongYinan
b4345d1375
fix(napi): block_on type (#1911) 2024-01-24 17:13:42 +08:00
Ranger
4d82737efe
chore: fix async_work status typo (#1883) 2024-01-02 13:23:45 +08:00
LongYinan
03eb476cef
Release independent packages 
- napi@2.14.2
 2023-12-31 22:08:11 +08:00
LongYinan
65273a4631
chore(napi): add status to error messages in AsyncWork (#1880) 2023-12-30 11:56:36 +08:00
LongYinan
43a080d52b
fix(napi): apply clippy suggestions (#1878) 2023-12-29 23:08:56 +08:00
renovate[bot]
8d3d60c356
fix(deps): update rust crate once_cell to 1.19 (#1845) 
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
 2023-12-07 22:23:43 +08:00
LongYinan
e4ac44e560
Release independent packages 
- napi@2.14.1
- napi-derive@2.14.2
 2023-11-20 17:18:35 +08:00
LongYinan
8a9c42a985
fix(napi): compile error for wasm32-unknown-unknown target 
- Close https://github.com/napi-rs/napi-rs/issues/1816
 2023-11-20 17:10:58 +08:00
LongYinan
7dced934a7
fix(napi): cargo doc build 
- Close https://github.com/napi-rs/napi-rs/issues/1800
 2023-11-20 16:22:21 +08:00
LongYinan
6a1943ba54
style(napi): clippy fix (#1815) 2023-11-17 20:42:53 +08:00
LongYinan
688ee04247
Release independent packages 
- napi-build@2.1.0
- napi-derive@2.14.0
- napi@2.14.0
- napi-sys@2.3.0
 2023-11-07 14:18:36 +08:00
LongYinan
36581336c6
feat(napi): pass the rest of async tests (#1792) 
Pass the rest of async tests, including await the JavaScript Promise in the Rust side, and the worker_threads tests.
 2023-11-07 01:46:43 +08:00
LongYinan
3deae16442
fix(napi): add tokio cleanup hook for more platforms (#1790) 2023-11-06 13:59:54 +08:00
LongYinan
65f57918fb
style(napi): as ptr => ptr::cast (#1786) 2023-11-06 11:22:30 +08:00
LongYinan
1e5c32ca60
style(napi): fix compile warning (#1785) 2023-11-06 11:21:26 +08:00
LongYinan
feabcd7f16
test(napi): add tests for napi9 features (#1784) 2023-11-06 11:03:44 +08:00
LongYinan
4e4d891ad8
feat: add experimental Env::get_module_file_name method (#1783) 2023-11-06 11:01:27 +08:00
LongYinan
2b0ddf4a21
feat(napi,sys): sync to napi9 (#1781) 
- Close https://github.com/napi-rs/napi-rs/issues/1600
 2023-11-06 11:00:27 +08:00
LongYinan
546b108a5b
feat(napi): support async class factory (#1779) 
- Close https://github.com/napi-rs/napi-rs/issues/1777
 2023-11-06 10:58:23 +08:00
LongYinan
0dc1ef738b fix(napi): asan caught memory safety issue 2023-11-04 15:26:07 +08:00
Özgür Akkurt
2c410b238d
feat(napi): impl Default for Buffer (#1734) 2023-11-02 22:32:13 +08:00
stefan-gorules
afdd4060ab
fix(napi): js promise error messages (#1672) 2023-11-02 17:32:20 +08:00
kuzeyardabulut
3a1a280d5f
fix(napi): potential double free issue (#1679) 
* Update module_register.rs

* Run fmt

---------

Co-authored-by: LongYinan <lynweklm@gmail.com>
 2023-11-02 17:19:35 +08:00
LongYinan
13d0ce075e
feat: integrate with emnapi (#1669) 
* Integrate with emnapi

* resolve conflict

* ignore wasm

* generate wasi file

* Add wasi test to workflow

* Fix wasi template

* emnapi new initialize api

* Finish test

* Purne tsconfig

* Generate wasi worker

* Fix electron test

* Finalize check

* Noop adjust_external_memory

* Apply cr suggestions
 2023-11-02 12:57:11 +08:00