Skip to content

chore(deps): update node.js to v20 #473

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 27, 2023

This PR contains the following updates:

Package Type Update Change Age Adoption Passing Confidence
node (source) major 16.19.1 -> 20.19.0 age adoption passing confidence
node (source) engines major ^16.14.2 -> ^20.0.0 age adoption passing confidence
@types/node (source) devDependencies major 16.18.16 -> 20.17.30 age adoption passing confidence

Release Notes

nodejs/node (node)

v20.19.0: 2025-03-13, Version 20.19.0 'Iron' (LTS), @​marco-ippolito

Compare Source

Notable Changes
require(esm) is now enabled by default

Support for loading native ES modules using require() had been available on v20.x under the command line flag --experimental-require-module, and available by default on v22.x and v23.x. In this release, it is now no longer behind a flag on v20.x.

This feature has been tested on v23.x and v22.x, and we are looking for user feedback from v20.x to make more final tweaks before fully stabilizing it. When the Node.js instance encounters a native ES module in require() somewhere outside node_modules for the first time, it will emit an experimental warning unless require() comes from a path that contains node_modules. If there happens to be any regressions caused by this feature, users can report it to the Node.js issue tracker. Meanwhile this feature can also be disabled using --no-experimental-require-module as a workaround.

With this feature enabled, Node.js will no longer throw ERR_REQUIRE_ESM if require() is used to load a ES module. It can, however, throw ERR_REQUIRE_ASYNC_MODULE if the ES module being loaded or its dependencies contain top-level await. When the ES module is loaded successfully by require(), the returned object will either be a ES module namespace object similar to what's returned by import(), or what gets exported as "module.exports" in the ES module.

Users can check process.features.require_module to see whether require(esm) is enabled in the current Node.js instance. For packages, the "module-sync" exports condition can be used as a way to detect require(esm) support in the current Node.js instance and allow both require() and import to load the same native ES module. See the documentation for more details about this feature.

Contributed by Joyee Cheung in #​55085

Module syntax detection is now enabled by default

Module syntax detection (the --experimental-detect-module flag) is now
enabled by default. Use --no-experimental-detect-module to disable it if
needed.

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 .js or no extension, where the nearest parent
package.json has 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" to
the nearest parent package.json file 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.

Other Notable Changes
  • [285bb4ee14] - crypto: update root certificates to NSS 3.107 (Node.js GitHub Bot) #​56566
  • [73b5c16684] - (SEMVER-MINOR) worker: add postMessageToThread (Paolo Insogna) #​53682
  • [de313b2336] - (SEMVER-MINOR) module: only emit require(esm) warning under --trace-require-module (Joyee Cheung) #​56194
  • [4fba01911d] - (SEMVER-MINOR) process: add process.features.require_module (Joyee Cheung) #​55241
  • [df8a045afe] - (SEMVER-MINOR) module: implement the "module-sync" exports condition (Joyee Cheung) #​54648
  • [f9dc1eaef5] - (SEMVER-MINOR) module: add __esModule to require()'d ESM (Joyee Cheung) #​52166
Commits

v20.18.3: 2025-02-10, Version 20.18.3 'Iron' (LTS), @​marco-ippolito

Compare Source

Notable Changes
Commits

Configuration

📅 Schedule: Branch creation - "after 4pm on friday,before 9am on monday,every weekend" in timezone Europe/Paris, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@netlify
Copy link

netlify bot commented Oct 27, 2023

Deploy Preview for algolia-ga-actions-netlify failed.

Name Link
🔨 Latest commit 873cb8e
🔍 Latest deploy log https://app.netlify.com/sites/algolia-ga-actions-netlify/deploys/67f00ab6d894f40008b2ad19

@github-actions
Copy link

Check your created Crawler

Check your created index on your Algolia Application

@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 97410d0 to aed9b81 Compare November 10, 2023 15:58
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 0b777d0 to 646d1d4 Compare November 18, 2023 21:19
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 1e8dcef to 7ad57d1 Compare December 1, 2023 16:03
@renovate renovate bot force-pushed the renovate/node-20.x branch 3 times, most recently from f0214d2 to 76e1de4 Compare December 8, 2023 15:36
@renovate renovate bot force-pushed the renovate/node-20.x branch from 76e1de4 to 7271634 Compare December 18, 2023 00:16
@renovate renovate bot force-pushed the renovate/node-20.x branch from 7271634 to 6aaacc9 Compare December 30, 2023 02:35
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from dce9f87 to 382a49f Compare January 12, 2024 16:22
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 6979145 to 4186095 Compare January 19, 2024 16:46
@renovate renovate bot force-pushed the renovate/node-20.x branch 4 times, most recently from c0965ea to 8369d27 Compare January 28, 2024 22:12
@renovate renovate bot force-pushed the renovate/node-20.x branch from 8369d27 to aa5d8de Compare February 2, 2024 16:12
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 32182f6 to cc0df28 Compare February 16, 2024 15:29
@renovate renovate bot force-pushed the renovate/node-20.x branch from cc0df28 to ac5d1ba Compare February 23, 2024 17:08
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from e0badbe to c590ae2 Compare March 8, 2024 17:40
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 1d5c8ff to 81babb4 Compare March 22, 2024 15:02
@renovate renovate bot force-pushed the renovate/node-20.x branch from 81babb4 to 6c8bde4 Compare March 29, 2024 16:26
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from f44483c to 128b3f4 Compare October 11, 2024 14:12
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 75ac2fd to ee7e6b4 Compare October 19, 2024 11:16
@renovate renovate bot force-pushed the renovate/node-20.x branch from ee7e6b4 to b21b1a6 Compare October 25, 2024 15:23
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 67af25f to 31d0781 Compare November 3, 2024 04:15
@renovate renovate bot changed the title chore(deps): update dependency node to v20 chore(deps): update node.js to v20 Nov 15, 2024
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 02abd1a to 13fd4f3 Compare November 23, 2024 11:55
@renovate renovate bot force-pushed the renovate/node-20.x branch from 13fd4f3 to 702cade Compare November 29, 2024 17:21
@renovate renovate bot force-pushed the renovate/node-20.x branch from 702cade to 96ca8a1 Compare December 13, 2024 15:56
@renovate renovate bot force-pushed the renovate/node-20.x branch from 96ca8a1 to c3253f0 Compare January 3, 2025 15:28
@renovate renovate bot force-pushed the renovate/node-20.x branch from c3253f0 to 948b089 Compare January 10, 2025 16:50
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 1000e8c to 229159b Compare January 24, 2025 15:37
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from be86b5a to 88744a2 Compare February 14, 2025 17:55
@renovate renovate bot changed the title chore(deps): update node.js to v20 chore(deps): update dependency @types/node to v20 Feb 21, 2025
@renovate renovate bot force-pushed the renovate/node-20.x branch 4 times, most recently from 2de9acc to 2a91c04 Compare March 7, 2025 17:25
@renovate renovate bot force-pushed the renovate/node-20.x branch from 2a91c04 to acf55a8 Compare March 9, 2025 02:59
@renovate renovate bot changed the title chore(deps): update dependency @types/node to v20 chore(deps): update node.js to v20 Mar 10, 2025
@renovate renovate bot force-pushed the renovate/node-20.x branch from acf55a8 to 2916381 Compare March 14, 2025 17:09
@renovate renovate bot force-pushed the renovate/node-20.x branch from 2916381 to fbde618 Compare March 21, 2025 17:24
@renovate renovate bot force-pushed the renovate/node-20.x branch from fbde618 to c30be72 Compare March 28, 2025 17:56
@renovate renovate bot force-pushed the renovate/node-20.x branch from c30be72 to 873cb8e Compare April 4, 2025 16:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants