Chris Harwood

I just ran into this, myself. I took at look at the rule, and we have: **/lib/rules/no-unsupported-features/es-syntax.js** ```js const features = { /* ... */ //-------------------------------------------------------------------------- // ES2020 //-------------------------------------------------------------------------- /*...

Incidentally, I'd be happy to make a PR for this, but I don't want to just submit one without any chance of it getting merged.

Okay all, here it is: https://github.com/mysticatea/eslint-plugin-node/pull/256 I ended up doing a small refactor that allows more-complex semver strings for rule cases that is hopefully not too controversial. Let me know...

@mysticatea Any thoughts on this?

To anyone following this issue, the change in https://github.com/mysticatea/eslint-plugin-node/pull/256 has been merged over in https://github.com/weiran-zsd/eslint-plugin-node as https://github.com/weiran-zsd/eslint-plugin-node/pull/13. It looks like, until there's any movement on this repository and we hear...

Looks like `certPath` is a possible property of the connection configuration. See here: https://github.com/Borvik/vscode-postgres/blob/master/src/common/database.ts#L76

I noticed the reference to my issue and thought I'd chime in: until that issue is resolved, once **chalk** has detected color is not supported, it's not possible to turn...

@Qix- You missed part of my quote: > [...] once chalk has detected color is not supported, it's not possible to turn it back on programmatically. That's the entire basis...

> @nazrhyn I saw your post; please see [#234 (comment)](https://github.com/chalk/chalk/issues/234#issuecomment-440326870). It was never 'broken', just not obvious. So, you guys asked me to create a failing unit test for something...

@Qix- Certainly wasn't trying to sound grouchy, rather just trying to keep tabs on the issue I submitted and understand how to use **chalk**. I'll move any further discussion about...