Audisho Sada

Hmmm. I'm not exactly sure what I'm doing wrong here. It's throwing within the test and failing, but not when I implement it in my project. Any thoughts? ``` test('allows...

I gave it a shot - https://github.com/pinojs/pino-debug/pull/28 credit to https://github.com/krakenjs/freshy for the code snippet

I'm seeing the same error on 3.0.2. No issues on 3.0.1. I'm using the following configuration type in my eslintrc file: `{ "plugins": ["no-unsanitized"], "extends": ["plugin:no-unsanitized/DOM"] }`

The error message and debug info don't appear to give much information. I'm using VS Code with the eslint plugin and the error pops up on every file with a...

I was able to trigger the error with the following file. ``` /* Foo.js */ import React, { Component } from 'react'; class Foo extends Component { render() { return...

Sure thing. Here's the full file. ``` module.exports = { "parser": "babel-eslint", "plugins": [ "react", "jsx-a11y", "no-unsanitized", "security", ], "extends": [ "eslint:recommended", "plugin:react/recommended", "plugin:jsx-a11y/recommended", "plugin:no-unsanitized/DOM", "plugin:security/recommended", ], "rules": { "comma-dangle":...

Reported it to Mozilla just in case it's their issue: https://bugzilla.mozilla.org/show_bug.cgi?id=1831438

With yarn, I was able to work-around this by adding "eslint" to "resolutions" in my `package.json`. ``` { // ... "resolutions": { "eslint": "^7.8.1" } } ``` I believe that...

@rubiin thank you for sharing! Just to confirm, does your config map these actions to separate key bindings? I was hoping to restore the same behavior as using the language...

I added the following to my config and now the actions show up with the other line specific actions. ```lua -- array of strings("fix_all"|"add_missing_imports"|"remove_unused"| -- "remove_unused_imports"|"organize_imports") -- or string "all"...