Open renovate[bot] opened 4 months ago
Thanks for opening an issue! Make sure you've followed CONTRIBUTING.md.
Is your PR ready for review and processing? Mark the PR ready by including #pr-ready
in a comment.
If you still have work to do, even after marking this ready. Put the PR on hold by including #pr-onhold
in a comment.
Thanks for the PR!
This section of the codebase is owner by https://github.com/AlexRogalskiy/ - if they write a comment saying "LGTM" then it will be merged.
This PR contains the following updates:
14.16.0
->22.8.0
Release Notes
nodejs/node (node)
### [`v22.8.0`](https://redirect.github.com/nodejs/node/releases/tag/v22.8.0): 2024-09-03, Version 22.8.0 (Current), @RafaelGSS [Compare Source](https://redirect.github.com/nodejs/node/compare/v20.17.0...v22.8.0) ##### New JS API for compile cache This release adds a new API `module.enableCompileCache()` that can be used to enable on-disk code caching of all modules loaded after this API is called. Previously this could only be enabled by the `NODE_COMPILE_CACHE` environment variable, so it could only set by end-users. This API allows tooling and library authors to enable caching of their own code. This is a built-in alternative to the [v8-compile-cache](https://www.npmjs.com/package/v8-compile-cache)/[v8-compile-cache-lib ](https://www.npmjs.com/package/v8-compile-cache-lib) packages, but have [better performance](https://redirect.github.com/nodejs/node/issues/47472#issuecomment-1970331362) and supports ESM. Thanks to Joyee Cheung for working on this. ##### New option for vm.createContext() to create a context with a freezable globalThis Node.js implements a flavor of `vm.createContext()` and friends that creates a context without contextifying its global object when vm.constants.DONT_CONTEXTIFY is used. This is suitable when users want to freeze the context (impossible when the global is contextified i.e. has interceptors installed) or speed up the global access if they don't need the interceptor behavior. Thanks to Joyee Cheung for working on this. ##### Support for coverage thresholds Node.js now supports requiring code coverage to meet a specific threshold before the process exits successfully. To use this feature, you need to enable the `--experimental-test-coverage` flag. You can set thresholds for the following types of coverage: - **Branch coverage**: Use `--test-coverage-branches=Configuration
📅 Schedule: Branch creation - "after 10pm every weekday,before 5am every weekday,every weekend" in timezone Europe/Moscow, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.