Commitment to Compatibility
The release of Neon 1.0 marks our commitment to backwards-compatibility: starting with 1.0.0, Neon users can be confident that future upgrades to Neon 1.x versions should never require code changes (with the possible exception of safety bugfixes, which we expect to be rare). We also do not anticipate releasing new major versions often and do not have any plans to do so for now.
Breaking Changes
- Remove the generic parameter from
JsFunction
(#989) JsArray::new
takes ausize
instead of au32
(#988)- Made
Context::global
read a key and addedContext::global_object
(#987) - Deprecated feature flags were removed
Bug fixes
- Fix
unhandledRejection
withJsPromise::to_future
(#1008) - Typo in
cargo-cp-artifact
help (#998) - Typo in README (#1012)
Other
- Relaxed error behavior on missing Node-API symbols. Neon will panic on first use instead of aborting the process at module load time.
- Bumped dependency versions
- Changed to edition 2021
- Updated support matrix to Node 18, 20, and 21