Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Deprecation warning since Node `14.5.0`

See original GitHub issue

Before you open this issue, please complete the following tasks:

use the search bar at the top of the page to search this repository for similar issues or discussions that have already been opened.
if you are looking for help from the gulp team or community, open a discussion.
if you think there is a problem with the plugin you’re using, open a discussion.
if you think there is a bug in our code, open this issue.

What were you expecting to happen?

No deprecation warning should be printed on the console since Node 14.5.0.

What actually happened?

A deprecation warning is printed on the console since Node 14.5.0.

(node:47881) [DEP0097] DeprecationWarning: Using a domain property in MakeCallback is deprecated. Use the async_context variant of MakeCallback or the AsyncResource class instead.

Please give us a sample of your gulpfile

const gulp = require('gulp')

module.exports.example = function () {
  return gulp.src([__filename])
}

$ gulp example
[01:17:58] Using gulpfile ~/Desktop/gulpfile.js
[01:17:58] Starting 'example'...
(node:47881) [DEP0097] DeprecationWarning: Using a domain property in MakeCallback is deprecated. Use the async_context variant of MakeCallback or the AsyncResource class instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
[01:17:58] Finished 'example' after 14 ms

Please provide the following information:

OS & version: Ubuntu 20.04
node version: v14.5.0
npm version: v6.14.5
gulp version: CLI version: 2.3.0, Local version: 4.0.2

Issue Analytics

State:
Created 3 years ago
Reactions:3
Comments:5 (1 by maintainers)

Top GitHub Comments

4reactions

noahbrennercommented, Jul 17, 2020

Looks like warning was the result of https://github.com/nodejs/node/pull/33801, but showing the warning was unintentional and was addressed by https://github.com/nodejs/node/pull/34245 (which was merged, despite the GitHub status shown). Hopefully that fix will show up in the next released node version.

3reactions

AlexanderOMaracommented, Jul 23, 2020

The deprecation warning is no longer shown in Node 14.6.0.