chore(deps): update all dependencies #33
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "renovate/all"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
3.3.31->3.3.32^4.17.6->^5.0.0^4.17.5->^5.0.022.8.4->22.9.1^20.0.0->^22.0.011.2.1->11.5.0^8.0.0->^9.0.013.14.0->13.16.0^3.0.0->^4.0.02.3.5->2.6.514 || 16 || 20->14 || 16 || 20 || 228.12.0->8.13.12.0.5->2.0.8~5.5.0->~5.6.03.14.2->3.17.0Release Notes
WiseLibs/better-sqlite3 (better-sqlite3)
v11.5.0Compare Source
What's Changed
Full Changelog: https://github.com/WiseLibs/better-sqlite3/compare/v11.4.0...v11.5.0
v11.4.0Compare Source
What's Changed
New Contributors
Full Changelog: https://github.com/WiseLibs/better-sqlite3/compare/v11.3.0...v11.4.0
v11.3.0Compare Source
What's Changed
Full Changelog: https://github.com/WiseLibs/better-sqlite3/compare/v11.2.1...v11.3.0
open-cli-tools/concurrently (concurrently)
v9.1.0Compare Source
What's Changed
New Contributors
Full Changelog: https://github.com/open-cli-tools/concurrently/compare/v9.0.1...v9.1.0
v9.0.1Compare Source
What's Changed
Full Changelog: https://github.com/open-cli-tools/concurrently/compare/v9.0.0...v9.0.1
v9.0.0Compare Source
💥 Breaking Changes
Dropped support for Node.js < 18.0.0.
Older Node.js version have reached end-of-life, and certain features require new-ish JS APIs.
Pending commands no longer run when
--max-processesis set and an interruption/kill signal is sent - #433, #452, #460Before v9.0.0, pressing Ctrl+C when
--max-processesis set meant that only those commands would receive it. Once these stopped, the pending commands would start, which in turn meant that another Ctrl+C press would be necessary to stop them, and so on.Similar situation applied to combining
--max-processeswith--kill-others/--kill-others-on-fail.Starting with v9.0.0, this no longer happens, as these flags and/or key presses send a signal to stop the running commands in addition to preventing new commands from running.
The
concurrentlyand default exports are now the same - #399It's reasonable to expect that
import { concurrently } from 'concurrently'would work the same asimport concurrently from 'concurrently', however this has not been the case.The former used to be an unconfigured version of concurrently, lacking all features that you'd get from the CLI, which was seen as a "footgun". Both are now the same function.
If you'd like to access the unconfigured function, use
import { createConcurrently } from 'concurrently'instead.✨ New Features
Use
--restart-after exponential. Restarts happen at2^Nseconds.--pad-prefixflag - #166, #417, #495--teardownflag - #472, #500node:<script>commands tonode --run <script>- #475statefield toCommand- #455🐛 Bug Fixes
spawn-commandwhen running in Node 22 - #407, #477, #479, #492--rawand--hidecompatible - #394, #486Other Changes
--helpno longer shows examples due to there being too many.Refer to https://github.com/open-cli-tools/concurrently/tree/v9.0.0/docs instead, or to the
node_modules/concurrently/docsdirectory in your project.--passthrough-arguments- #490date-fnswith hand-rolled date formatting - #436, #443This should make installing concurrently faster.
New Contributors
Full Changelog: https://github.com/open-cli-tools/concurrently/compare/v8.2.2...v9.0.0
cypress-io/cypress (cypress)
v13.16.0Compare Source
Changelog: https://docs.cypress.io/guides/references/changelog#13-16-0
v13.15.2Compare Source
Changelog: https://docs.cypress.io/guides/references/changelog#13-15-2
v13.15.1Compare Source
Changelog: https://docs.cypress.io/guides/references/changelog#13-15-1
v13.15.0Compare Source
Changelog: https://docs.cypress.io/guides/references/changelog#13-15-0
v13.14.2Compare Source
Changelog: https://docs.cypress.io/guides/references/changelog#13-14-2
v13.14.1Compare Source
Changelog: https://docs.cypress.io/guides/references/changelog#13-14-1
cypress-io/eslint-plugin-cypress (eslint-plugin-cypress)
v4.1.0Compare Source
Features
v4.0.0Compare Source
Features
BREAKING CHANGES
Support for ESlint v7 & v8 is removed
languageOptions ecmaVersion: 2019 and sourceType: module are removed from eslint-plugin-cypress/flat config
globals is updated to 15.11.0
eslint-plugin-n is updated to 17.11.1
v3.6.0Compare Source
Features
mswjs/msw (msw)
v2.6.5Compare Source
v2.6.5 (2024-11-16)
Bug Fixes
5bf3e3b) @kettanaitov2.6.4Compare Source
v2.6.4 (2024-11-10)
Bug Fixes
sendBeacon()requests (#2353) (2fa98c3) @kettanaito2fa98c3) @kettanaitov2.6.3Compare Source
v2.6.3 (2024-11-10)
Bug Fixes
transformResponseoption (#2351) (74c4a3a) @kettanaitov2.6.2Compare Source
v2.6.2 (2024-11-07)
Bug Fixes
@bundled-es-modules/cookieto 2.0.1 (#2312) (c134352) @kettanaitov2.6.1Compare Source
v2.6.1 (2024-11-06)
Bug Fixes
instanceofhandler check failures between different MSW versions (#2349) (28d26bd) @kettanaitov2.6.0Compare Source
v2.6.0 (2024-10-29)
Features
ae786f5) @kettanaito @DanielleHuismanv2.5.2Compare Source
v2.5.2 (2024-10-27)
Bug Fixes
e9b0636) @kettanaitov2.5.1Compare Source
v2.5.1 (2024-10-24)
Bug Fixes
@inquirer/confirmrequirement to 5.0.0 (#2325) (b65c0a8) @greysteil @kettanaitov2.5.0Compare Source
v2.5.0 (2024-10-22)
Features
a1a81ba) @kettanaitov2.4.13Compare Source
v2.4.13 (2024-10-22)
Bug Fixes
@inquirer/confirmto 4.0 (#2300) (0cf9cce) @greysteil @kettanaitov2.4.12Compare Source
v2.4.12 (2024-10-21)
Bug Fixes
a58a300) @paoloricciutiv2.4.11Compare Source
v2.4.11 (2024-10-14)
Bug Fixes
8f68f0a) @kettanaitov2.4.10Compare Source
v2.4.10 (2024-10-11)
Bug Fixes
8e40724) @kettanaitov2.4.9Compare Source
v2.4.9 (2024-09-20)
Bug Fixes
Requestas init when recording raw headers (#2293) (bf982ea) @kettanaitov2.4.8Compare Source
v2.4.8 (2024-09-17)
Bug Fixes
expressandpath-to-regexpvulnerabilities (#2285) (e3487bc) @markmssdv2.4.7Compare Source
v2.4.7 (2024-09-15)
Bug Fixes
e04eb8f) @kettanaitoObject.definePropertyfor Headers proxy (#2283) (94e17be) @kettanaitov2.4.6Compare Source
v2.4.6 (2024-09-13)
Bug Fixes
397444b) @kettanaitov2.4.5Compare Source
v2.4.5 (2024-09-11)
Bug Fixes
max-age=0from cookie store (#2275) (c307ab2) @kettanaitov2.4.4Compare Source
v2.4.4 (2024-09-08)
Bug Fixes
f5785bf) @kettanaitov2.4.3Compare Source
v2.4.3 (2024-09-07)
Bug Fixes
7cd39e7) @kettanaitov2.4.2Compare Source
v2.4.2 (2024-09-04)
Bug Fixes
initcommand (#2260) (ba285b8) @ivanfernandez2646 @kettanaito6b2a7e6) @THETCR @kettanaitographqlimport as require in cjs (#2258) (b977602) @kettanaitov2.4.1Compare Source
v2.4.1 (2024-08-29)
Bug Fixes
graphqllazily (#2250) (1799e06) @kettanaitographqlto "peerDependencies" (#2249) (8a9568a) @THETCRv2.4.0Compare Source
v2.4.0 (2024-08-28)
Features
HttpResponse.html()static method (#2140, docs) (8c5580a) @scruffymongrel @kettanaito40b17fd) @kettanaitoonUnhandledRequestmessage (#2227) (a2153c9) @bitttttten @kettanaitonodejs/node (node)
v22.11.0: 2024-10-29, Version 22.11.0 'Jod' (LTS), @richardlauCompare Source
Notable Changes
This release marks the transition of Node.js 22.x into Long Term Support (LTS)
with the codename 'Jod'. The 22.x release line now moves into "Active LTS"
and will remain so until October 2025. After that time, it will move into
"Maintenance" until end of life in April 2027.
Other than updating metadata, such as the
process.releaseobject, to reflectthat the release is LTS, no further changes from Node.js 22.10.0 are included.
OpenSSL 3.x
Official binaries for Node.js 22.x currently include OpenSSL 3.0.x (more
specifically, the quictls OpenSSL fork).
OpenSSL 3.0.x is the currently designated long term support version that is
scheduled to be supported until 7th September 2026, which is within the expected
lifetime of Node.js 22.x. We are expecting upstream OpenSSL to announce a
successor long term support version prior to that date and since OpenSSL now
follows a semantic versioning-like versioning scheme we expect to be able to
update to the next long term supported version of OpenSSL during the lifetime of
Node.js 22.x.
v22.10.0: 2024-10-16, Version 22.10.0 (Current), @aduh95Compare Source
Notable Changes
New
"module-sync"exports conditionThis release introduces a
"module-sync"exports condition that's enabled whenrequire(esm)is enabled, so packages can supply a synchronous ES module to theNode.js module loader, no matter if it's being required or imported. This is
similar to the
"module"condition that bundlers have been using to supportrequire(esm)in Node.js, and allows dual-package authors to opt into ESM-firstonly on newer versions of Node.js that supports
require(esm)to avoid thedual-package hazard.
Or if the package is only meant to be run on Node.js and wants to fallback to
CJS on older versions that don't have
require(esm):For package authors: this only serves as a feature-detection mechanism for
packages that wish to support both CJS and ESM users during the period when some
active Node.js LTS versions support
require(esm)while some older ones don't.When all active Node.js LTS lines support
require(esm), packages can simplifytheir distributions by bumping the major version, dropping their CJS exports,
and removing the
module-syncexports condition (with onlymainordefaulttargetting the ESM exports). If the package needs to support both bundlers and
being run unbundled on Node.js during the transition period, use both
module-syncandmoduleand point them to the same ESM file. If the packagealready doesn't want to support older versions of Node.js that doesn't support
require(esm), don't use this export condition.For bundlers/tools: they should avoid implementing this stop-gap condition.
Most existing bundlers implement the de-facto bundler standard
moduleexports condition, and that should be enough to support users who want to bundle
ESM from CJS consumers. Users who want both bundlers and Node.js to recognize
the ESM exports can use both
module/module-syncconditions during thetransition period, and can drop
module-sync+modulewhen they no longer needto support older versions of Node.js. If tools do want to support this
condition, it's recommended to make the resolution rules in the graph pointed by
this condition match the Node.js native ESM rules to avoid divergence.
We ended up implementing a condition with a different name instead of reusing
"module", because existing code in the ecosystem using the"module"condition sometimes also expect the module resolution for these ESM files to
work in CJS style, which is supported by bundlers, but the native Node.js loader
has intentionally made ESM resolution different from CJS resolution (e.g.
forbidding
import './noext'orimport './directory'), so it would bebreaking to implement a
"module"condition without implementing the forbiddenESM resolution rules. For now, this just implements a new condition as
semver-minor so it can be backported to older LTS.
Contributed by Joyee Cheung in #54648.
node --runis now stableThis CLI flag runs a specified command from a
package.json's"scripts"object.For the following
package.json:You can run
node --run testand that would start the test suite.Contributed by Yagiz Nizipli in #53763.
Other notable changes
Commits
v22.9.0: 2024-09-17, Version 22.9.0 (Current), @RafaelGSSCompare Source
New API to retrieve execution Stack Trace
A new API
getCallSitehas been introduced to theutilmodule. This API allows usersto retrieve the stacktrace of the current execution. Example:
Thanks to Rafael Gonzaga for making this work on #54380.
Disable V8 Maglev
We have seen several crashes/unexpected JS behaviors with maglev on v22
(which ships V8 v12.4). The bugs lie in the codegen so it would be difficult for
users to work around them or even figure out where the bugs are coming from.
Some bugs are fixed in the upstream while some others probably remain.
As v22 will get stuck with V8 v12.4 as LTS, it will be increasingly difficult to
backport patches for them even if the bugs are fixed. So disable it by default
on v22 to reduce the churn and troubles for users.
Thanks to Joyee Cheung for making this work on #54384
Exposes X509_V_FLAG_PARTIAL_CHAIN to tls.createSecureContext
This releases introduces a new option to the API
tls.createSecureContext. Fornow on users can use
tls.createSecureContext({ allowPartialTrustChain: true })to treat intermediate (non-self-signed) certificates in the trust CA certificate
list as trusted.
Thanks to Anna Henningsen for making this work on #54790
Other Notable Changes
Deprecations
Commits
v22.8.0: 2024-09-03, Version 22.8.0 (Current), @RafaelGSSCompare Source
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_CACHEenvironment 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/v8-compile-cache-lib packages,
but have better performance 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 globalobject 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-coverageflag.You can set thresholds for the following types of coverage:
--test-coverage-branches=<threshold>--test-coverage-functions=<threshold>--test-coverage-lines=<threshold><threshold>should be an integer between 0 and 100. If an invalid value is provided, aTypeErrorwill be thrown.If the code coverage fails to meet the specified thresholds for any category, the process will exit with code
1.For instance, to enforce a minimum of 80% line coverage and 60% branch coverage, you can run:
Thanks Aviv Keller for working on this.
Other Notable Changes
Commits
v22.7.0: 2024-08-22, Version 22.7.0 (Current), @RafaelGSSCompare Source
Experimental transform types support
With the new flag
--experimental-transform-typesit is possible to enable thetransformation of TypeScript-only syntax into JavaScript code.
This feature allows Node.js to support TypeScript syntax such as
Enumandnamespace.Thanks to Marco Ippolito for making this work on #54283.
Module syntax detection is now enabled by default.
Module syntax detection (the
--experimental-detect-moduleflag) is nowenabled by default. Use
--no-experimental-detect-moduleto disable it ifneeded.
Syntax detection attempts to run ambiguous files as CommonJS, and if the module
fails to parse as CommonJS due to ES module syntax, Node.js tries again and runs
the file as an ES module.
Ambiguous files are those with a
.jsor no extension, where the nearest parentpackage.jsonhas no"type"field (either"type": "module"or"type": "commonjs").Syntax detection should have no performance impact on CommonJS modules, but it
incurs a slight performance penalty for ES modules; add
"type": "module"tothe nearest parent
package.jsonfile to eliminate the performance cost.A use case unlocked by this feature is the ability to use ES module syntax in
extensionless scripts with no nearby
package.json.Thanks to Geoffrey Booth for making this work on #53619.
Performance Improvements to Buffer
Performance of Node.js Buffers have been optimized through multiple PR's with significant
improvements to the
Buffer.copyandBuffer.writemethods. These are used throughoutthe codebase and should give a nice boost across the board.
Thanks to Robert Nagy for making this work on #54311,
#54324, and #54087.
Other Notable Changes
Commits
v22.6.0: 2024-08-06, Version 22.6.0 (Current), @RafaelGSSCompare Source
Experimental TypeScript support via strip types
Node.js introduces the
--experimental-strip-typesflag for initial TypeScript support.This feature strips type annotations from .ts files, allowing them to run
without transforming TypeScript-specific syntax. Current limitations include:
enumsornamespaces.Thanks Marco Ippolito for working on this.
Experimental Network Inspection Support in Node.js
This update introduces the initial support for network inspection in Node.js.
Currently, this is an experimental feature, so you need to enable it using the
--experimental-network-inspectionflag.With this feature enabled, you can inspect network activities occurring within a JavaScript application.
To use network inspection, start your Node.js application with the following command:
Please note that the network inspection capabilities are in active development.
We are actively working on enhancing this feature and will continue to expand its functionality in future updates.
httpandhttpsmodules only.feature request on the Chrome DevTools side is addressed.
Thanks Kohei Ueno for working on this.
Other Notable Changes
Commits
v22.5.1: 2024-07-19, Version 22.5.1 (Current), @richardlauCompare Source
Notable Changes
This release fixes a regression introduced in Node.js 22.5.0. The problem is known to display the following symptoms:
FATAL ERROR: v8::Object::GetCreationContextChecked No creation context available#53902npm error Exit handler never called!npm/cli#7657Usage Error: Couldn't find the node_modules state file - running an install might help (findPackageLocation)yarnpkg/berry#6398Commits
v22.5.0: 2024-07-17, Version 22.5.0 (Current), @RafaelGSS prepared by @aduh95Compare Source
Notable Changes
Commits
v22.4.1: 2024-07-08, Version 22.4.1 (Current), @RafaelGSSCompare Source
This is a security release.
Notable Changes
Commits
v22.4.0: 2024-07-02, Version 22.4.0 (Current), @targosCompare Source
Notable Changes
Experimental Web Storage API
API stability updates
Other Notable Changes
Commits
v22.3.0: 2024-06-11, Version 22.3.0 (Current), @RafaelGSSCompare Source
Notable Changes
Commits
v22.2.0: 2024-05-15, Version 22.2.0 (Current), @targosCompare Source
Notable Changes
Commits
v22.1.0: 2024-05-02, Version 22.1.0 (Current), @targos prepared by @aduh95Compare Source
module: implement
NODE_COMPILE_CACHEfor automatic on-disk code cachingThis patch implements automatic on-disk code caching that can be enabled
via an environment variable
NODE_COMPILE_CACHE=/path/to/cache/dir.When set, whenever Node.js compiles a CommonJS or a ECMAScript Module,
it will use on-disk V8 code cache
persisted in the specified directory
to speed up the compilation. This may slow down the first load of a
module graph, but subsequent loads of the same module graph may get
a significant speedup if the contents of the modules do not change.
Locally, this speeds up loading of
test/fixtures/snapshot/typescript.jsfrom ~130ms to ~80ms.
To clean up the generated code cache, simply remove the directory.
It will be recreated the next time the same directory is used for
NODE_COMPILE_CACHE.Compilation cache generated by one version of Node.js may not be used
by a different version of Node.js. Cache generated by different versions
of Node.js will be stored separately if the same directory is used
to persist the cache, so they can co-exist.
Caveat: currently when using this with V8 JavaScript code coverage, the
coverage being collected by V8 may be less precise in functions that are
deserialized from the code cache. It's recommended to turn this off when
running tests to generate precise coverage.
Contributed by Joyee Cheung in #52535.
Other Notable Changes
Commits
v22.0.0: 2024-04-24, Version 22.0.0 (Current), @RafaelGSS and @marco-ippolitoCompare Source
We're excited to announce the release of Node.js 22!
Highlights include require()ing ESM graphs, WebSocket client, updates of the V8 JavaScript engine, and more!
As a reminder, Node.js 22 will enter long-term support (LTS) in October, but until then, it will be the "Current" release for the next six months.
We encourage you to explore the new features and benefits offered by this latest release and evaluate their potential impact on your applications.
Other Notable Changes
Semver-Major Commits
Semver-Minor Commits
Semver-Patch Commits
brianc/node-postgres (pg)
v8.13.1Compare Source
v8.13.0Compare Source
bahmutov/start-server-and-test (start-server-and-test)
v2.0.8Compare Source
Bug Fixes
v2.0.7Compare Source
Bug Fixes
v2.0.6Compare Source
Bug Fixes
microsoft/TypeScript (typescript)
v5.6.3: TypeScript 5.6.3Compare Source
For release notes, check out the release announcement.
For the complete list of fixed issues, check out the
Downloads are available on:
v5.6.2: TypeScript 5.6Compare Source
For release notes, check out the release announcement.
For the complete list of fixed issues, check out the
Downloads are available on:
winstonjs/winston (winston)
v3.17.0Compare Source
3e8712869625fc876ef7a7ef2c1dfe4b64ec9fd9a414fef0f545b683cceb265bb529b6ae847abv3.16.0Compare Source
201b6f1v3.15.0Compare Source
Note: we removed LogCallback from the TS definitions because the underlying library didn't actually support these. If this causes issues in your apps, we recommend you remove references to LogCallbacks, since such code was not being executed anyways. See #2513 and the issue linked therein.
3a54777f110f61f5dde86d1b8dc6564161aeb7e31522aab6dConfiguration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Renovate Bot.
chore(deps): update dependency @types/node to v20.16.1to chore(deps): update dependency @types/node to v20.16.206bd267ce2to46acf0b4e2chore(deps): update dependency @types/node to v20.16.2to chore(deps): update all dependencies46acf0b4e2tobae6709207bae6709207to63d81f4ad063d81f4ad0toe8c1afbe7be8c1afbe7bto7f15d449037f15d44903to77dba9953f77dba9953fto1ddf829ec31ddf829ec3to295c27b6a8295c27b6a8toefb49385d9efb49385d9to05ce64566b05ce64566bto8076b1e3e88076b1e3e8to792adcb181792adcb181to8ee767a6358ee767a635toa227262b2aa227262b2atof0627c7037f0627c7037to866926c749866926c749to747b490cb6747b490cb6to727f21ab37727f21ab37to4a2f8faa214a2f8faa21tob68d792237b68d792237to79b719310a79b719310ato5c8c7ef1a95c8c7ef1a9tobd4a6756c5bd4a6756c5to313330c7b7313330c7b7toe29eceef29e29eceef29to441a563ba1441a563ba1toa7cbe72b6ca7cbe72b6ctoeace3db6f0eace3db6f0to530e8588f8530e8588f8todd6062a260dd6062a260to32fe6c79b432fe6c79b4to86a23876a386a23876a3to9e722bf8e29e722bf8e2to072bcd84dc072bcd84dctod034d8de9ad034d8de9atof708e8c9f1f708e8c9f1to74dbe8867c74dbe8867ctobcca8e1455bcca8e1455tofc21709e5ffc21709e5ftocef44b9a68cef44b9a68to8418bc581f8418bc581fto1c3573bc651c3573bc65to0d25159b9c0d25159b9cto5e266fc1855e266fc185to56db7e3fa556db7e3fa5to720188ab4b720188ab4bto937d721755937d721755to182735a61b182735a61bto2899edf7172899edf717to61ab895ddd61ab895dddtocfed5cfe77cfed5cfe77to8f44b05b508f44b05b50to6bcefddae66bcefddae6to77d03c2ff277d03c2ff2to88692a004e88692a004etoac872f21c9ac872f21c9to93e7108df393e7108df3to8ba5672a4b8ba5672a4bto00211a3d1a00211a3d1ato3e532317343e53231734toa9e61819bca9e61819bctob269d2f550b269d2f550tob7f524cbd0b7f524cbd0to77e931eb5477e931eb54to7fdf8378587fdf837858to06ea40a31506ea40a315to33435fe51e33435fe51eto84d0ab79d084d0ab79d0toe4c129d60ae4c129d60ato7b3fbaddd27b3fbaddd2tod4ce452036d4ce452036to15d0cbbebb15d0cbbebbto09bead9b6709bead9b67to40ac2a7f3240ac2a7f32to604241f66c604241f66cto1e332465dd1e332465ddto7c81c4df5e7c81c4df5etof25b8c6d69Checkout
From your project repository, check out a new branch and test the changes.