emnapi
1.11.3 · 25 Jul 2026MIT633.5k / weekRepositoryHomepagenpmAtom feed
Upgrading emnapi From 0.38.1 to 1.11.3
36 releases in betweenevery note read
Reading releases, release notes and advisories…
- 7
- changes to make
- 0
- advisories fixed
- 29
- new
- 31
- fixes
Before you upgrade
Tick each one off as you go- Breaking1.10.0
- Breaking0.44.0
- Breaking0.44.0
- Breaking0.44.0
- Breaking0.44.0
- Breaking0.43.0
- Breaking0.43.0
Release by release
- Fixed
runtime: Define deferred state as own properties
- Fixed
Refresh memory views after unshared memory growth (v1.x backport)
- Fixed
- Fixed
Bind captured setImmediate to the global receiver
- Fixed
- Fixed
Refresh stale shared memory buffer before atomic access (v1.x backport)
- Fixed
- New
Add napi_create_external_sharedarraybuffer
- New
Support SharedArrayBuffer in napi_create_typedarray
- New
- Breaking
napi_adjust_external_memoryno longer grow wasm memory - Fixed
Early update wasm memory for views (github.com/hardfist/emnapi-shared-memory-grow-r…)
- Fixed
Add missing
from64wrap - Fixed
Coalesce tsfn (js version) send message
- Breaking
- Fixed
Allow maximum memory 4GB
- Fixed
1.9.1nothing new or fixed in the note
- New
Add required config hint in package entry
- Fixed
Fix data race and use-after-free in napi_threadsafe_function
- Fixed
Execute tsfn finalizer after queue drains when aborted
- New
25 other lines we could not sort, mostly version bumps
- 1.9.0
Rename node_api_create_object_with_properties
- 1.7.1
Move Node-API version detection
- 1.4.3
Update @emnapi/wasi-threads@1.0.2 in the package.json dependency of @emnapi/core
- 1.4.0
Define NAPI_VERSION 10
- 1.3.0
Update libuv source
- 0.45.0
feat: separate transformer packages
- 0.45.0
fix: incorrect result of
napi_create_bigint_uint64when the input is greater than0x7fffffffffffffff - 0.45.0
build: prebuilt library is built by LLVM 17 (wasi-sdk-21 & emscripten 3.1.44)
- 0.45.0
refactor: factor out common code into macros
- 0.45.0
refactor: migrate to ESM
19 internal lines (docs, tests, tooling) left out.
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.