Skip to content
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.

Sign up for GitHub

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

Jump to bottom

chore(deps): update node.js to v14 #120

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

chore(deps): update node.js to v14 #120

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Feb 3, 2021 •
edited
Loading

This PR contains the following updates:

Package Type Update Change Age Adoption Passing Confidence
node stage major 12.20.1-alpine3.10 -> 14.17.0-alpine3.10 age adoption passing confidence
@types/node (source) devDependencies minor 14.14.22 -> 14.18.63 age adoption passing confidence

Release Notes

nodejs/node (node)

v14.17.0: 2021-05-11, Version 14.17.0 'Fermium' (LTS), @​danielleadams

Compare Source

Notable Changes
Diagnostics channel (experimental module)

diagnostics_channel is a new experimental module that provides an API to create named channels to report arbitrary message data for diagnostics purposes.

The module was initially introduced in Node.js v15.1.0 and is backported to v14.17.0
to enable testing it at a larger scale.

With diagnostics_channel, Node.js core and module authors can publish contextual data about what they are doing at a given time. This could be the hostname and query string of a mysql query, for example. Just create a named channel with dc.channel(name) and call channel.publish(data) to send the data to any listeners to that channel.

const dc = require('diagnostics_channel');
const channel = dc.channel('mysql.query');

MySQL.prototype.query = function query(queryString, values, callback) {
  // Broadcast query information whenever a query is made
  channel.publish({
    query: queryString,
    host: this.hostname,
  });

  this.doQuery(queryString, values, callback);
};

Channels are like one big global event emitter but are split into separate objects to ensure they get the best performance. If nothing is listening to the channel, the publishing overhead should be as close to zero as possible. Consuming channel data is as easy as using channel.subscribe(listener) to run a function whenever a message is published to that channel.

const dc = require('diagnostics_channel');
const channel = dc.channel('mysql.query');

channel.subscribe(({ query, host }) => {
  console.log(`mysql query to ${host}: ${query}`);
});

The data captured can be used to provide context for what an app is doing at a given time. This can be used for things like augmenting tracing data, tracking network and filesystem activity, logging queries, and many other things. It's also a very useful data source for diagnostics tools to provide a clearer picture of exactly what the application is doing at a given point in the data they are presenting.

Contributed by Stephen Belanger #​34895.

UUID support in the crypto module

The new crypto.randomUUID() method now allows to generate random
RFC 4122 Version 4 UUID strings:

const { randomUUID } = require('crypto');

console.log(randomUUID());
// 'aa7c91a1-f8fc-4339-b9db-f93fc7233429'

Contributed by James M Snell #​36729.

Experimental support for AbortController and AbortSignal

Node.js 14.17.0 adds experimental partial support for AbortController and AbortSignal.

Both constructors can be enabled globally using the --experimental-abortcontroller flag.

Additionally, several Node.js APIs have been updated to support AbortSignal for cancellation.
It is not mandatory to use the built-in constructors with them. Any spec-compliant third-party alternatives
should be compatible.

AbortSignal support was added to the following methods:

  • child_process.exec
  • child_process.execFile
  • child_process.fork
  • child_process.spawn
  • dgram.createSocket
  • events.on
  • events.once
  • fs.readFile
  • fs.watch
  • fs.writeFile
  • http.request
  • https.request
  • http2Session.request
  • The promisified variants of setImmediate and setTimeout
Other notable changes
  • doc:
    • revoke deprecation of legacy url, change status to legacy (James M Snell) #​37784
    • add legacy status to stability index (James M Snell) #​37784
    • upgrade stability status of report API (Gireesh Punathil) #​35654
  • deps:
    • V8: Backport various patches for Apple Silicon support (BoHong Li) #​38051
    • update ICU to 68.1 (Michaël Zasso) #​36187
    • upgrade to libuv 1.41.0 (Colin Ihrig) #​37360
  • http:
    • add http.ClientRequest.getRawHeaderNames() (simov) #​37660
    • report request start and end with diagnostics_channel (Stephen Belanger) #​34895
  • util:
    • add getSystemErrorMap() impl (eladkeyshawn) #​38101
Commits

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.

@renovate renovate bot changed the title Update dependency @types/node to v14.14.23 Update dependency @types/node to v14.14.24 Feb 4, 2021
@renovate renovate bot changed the title Update dependency @types/node to v14.14.24 Update dependency @types/node to v14.14.25 Feb 4, 2021
@renovate renovate bot changed the title Update dependency @types/node to v14.14.25 Update dependency @types/node to v14.14.26 Feb 11, 2021
@renovate renovate bot changed the title Update dependency @types/node to v14.14.26 Update dependency @types/node to v14.14.27 Feb 12, 2021
@renovate renovate bot changed the title Update dependency @types/node to v14.14.27 Update dependency @types/node to v14.14.28 Feb 14, 2021
@renovate renovate bot changed the title Update dependency @types/node to v14.14.28 Update dependency @types/node to v14.14.29 Feb 18, 2021
@renovate renovate bot changed the title Update dependency @types/node to v14.14.29 Update dependency @types/node to v14.14.30 Feb 19, 2021
@renovate renovate bot changed the title Update dependency @types/node to v14.14.30 Update dependency @types/node to v14.14.31 Feb 19, 2021
@renovate renovate bot changed the title Update dependency @types/node to v14.14.31 Update dependency @types/node to v14.14.32 Mar 7, 2021
@renovate renovate bot changed the title Update dependency @types/node to v14.14.32 Update dependency @types/node to v14.14.33 Mar 9, 2021
@renovate renovate bot changed the title Update dependency @types/node to v14.14.33 Update dependency @types/node to v14.14.34 Mar 12, 2021
@renovate renovate bot changed the title Update dependency @types/node to v14.14.34 Update dependency @types/node to v14.14.35 Mar 15, 2021
@renovate renovate bot changed the title Update dependency @types/node to v14.14.35 Update dependency @types/node to v14.14.36 Mar 25, 2021
@renovate renovate bot changed the title Update dependency @types/node to v14.14.36 Update dependency @types/node to v14.14.37 Mar 27, 2021
@renovate renovate bot changed the title Update dependency @types/node to v14.14.37 Update dependency @types/node to v14.14.39 Apr 14, 2021
@renovate renovate bot changed the title Update dependency @types/node to v14.18.50 Update dependency @types/node to v14.18.51 Jun 13, 2023
@renovate renovate bot changed the title Update dependency @types/node to v14.18.51 Update dependency @types/node to v14.18.52 Jun 26, 2023
@renovate renovate bot changed the title Update dependency @types/node to v14.18.52 Update dependency @types/node to v14.18.53 Jul 1, 2023
@renovate renovate bot changed the title Update dependency @types/node to v14.18.53 Update dependency @types/node to v14.18.54 Jul 21, 2023
@renovate renovate bot changed the title Update dependency @types/node to v14.18.54 Update dependency @types/node to v14.18.55 Aug 22, 2023
@renovate renovate bot changed the title Update dependency @types/node to v14.18.55 Update dependency @types/node to v14.18.56 Aug 23, 2023
@renovate renovate bot changed the title Update dependency @types/node to v14.18.56 Update dependency @types/node to v14.18.57 Sep 1, 2023
@renovate renovate bot changed the title Update dependency @types/node to v14.18.57 Update dependency @types/node to v14.18.58 Sep 2, 2023
@renovate renovate bot changed the title Update dependency @types/node to v14.18.58 Update dependency @types/node to v14.18.59 Sep 8, 2023
@renovate renovate bot changed the title Update dependency @types/node to v14.18.59 Update dependency @types/node to v14.18.60 Sep 15, 2023
@renovate renovate bot changed the title Update dependency @types/node to v14.18.60 Update dependency @types/node to v14.18.61 Sep 16, 2023
@renovate renovate bot changed the title Update dependency @types/node to v14.18.61 Update dependency @types/node to v14.18.63 Oct 1, 2023
@renovate renovate bot changed the title Update dependency @types/node to v14.18.63 Update Node.js to v14 Dec 3, 2023
@renovate renovate bot changed the title Update Node.js to v14 Update node Docker tag to v14 Aug 6, 2024
@renovate renovate bot changed the title Update node Docker tag to v14 Update Node.js to v14 Aug 28, 2024
@renovate renovate bot changed the title Update Node.js to v14 chore(deps): update node.js to v14 Sep 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants