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.

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

Fix: update custom inspection to use a symbol #141

Merged
merged 1 commit into from Jun 22, 2018

Conversation

BridgeAR
Copy link
Contributor

Node.js 11 removed support for the inspect property on objects as
custom inspect functions. Instead, this can be done by using the
util.inspect.custom symbol that is used here instead. To keep it
backwarts compatible the old function stays in place.

The README actually has a reference to this as well. However, the old
inspect function will not be called by Node.js 11 anymore. I am not really
sure how to properly reflect that and just kept it as it is.

@phated
Copy link
Member

phated commented May 28, 2018

Yay more API churn /sarcasm

Also, failing tests.

Node.js 11 removed support for the `inspect` property on objects as
custom inspect functions. Instead, this can be done by using the
util.inspect.custom symbol that is used here instead. To keep it
backwarts compatible the old function stays in place.
@BridgeAR
Copy link
Contributor Author

The test is fixed. I just want to point out that this only failed on Node.js < 6. Node.js < 6 does not receive any security updates anymore and 6 is currently the newest version tested against. Shall I open a PR to test on newer versions as well and are there any plans to drop support for the older versions?

@phated
Copy link
Member

phated commented May 28, 2018

The test is fixed. I just want to point out that this only failed on Node.js < 6. Node.js < 6 does not receive any security updates anymore and 6 is currently the newest version tested against. Shall I open a PR to test on newer versions as well and are there any plans to drop support for the older versions?

We support back to node 0.10 - there is no reason to stop supporting old versions of node at this juncture because we are a build tool...

@BridgeAR
Copy link
Contributor Author

@phated please rerun the failures - they both should be either infrastructure failures while the one on travis could also be an issue with dev dependencies not supporting 0.10 anymore.

@BridgeAR
Copy link
Contributor Author

Ping @phated the tests have to be partially triggered again. The code should be fine.

@phated phated merged commit 2e5d7af into gulpjs:master Jun 22, 2018
@phated
Copy link
Member

phated commented Jun 22, 2018

Thanks @BridgeAR

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.

None yet

2 participants