The max-classes-per-file rule is enabled in rules/best-practices.js but there is no mention of this requirement in the docs. If this is a best practice, I'd like to know why.

https://eslint.org/docs/rules/func-call-spacing

When calling a function, developers may insert optional whitespace between the function’s name and the parentheses that invoke it.

Option: "never" (default) disallows space between the function name and the opening parenthesis.

Examples of incorrect code for this rule with the default "never" option:

/*eslint func-call-spacin

feature suggestion

Hey,

I suggest to use a standard documentation format like JSDoc to document all functions and APIs. Otherwise, you can use long strings as name for test cases, instead of just writing the name of the function being tested. This will improve readability of code and ensure better practices by people using it. Thanks.

Documentation for capIsNewExceptionPattern says the following:

allows any uppercase-started function names that match the specified regex pattern to be called without the new operator.

However, the actual behaviour seems to be that entire call expression is matched against the pa

Hi, I'm a Redux maintainer. I'd like to offer a couple suggestions.

Problem

The current Redux example implementation shows use of reducers with "hand-written" immutable update logic, and has a somewhat complex store configuration. In addition, the project currently uses a "folder-by-type" folder structure.

Proposed Solution

The project should switch to using the official [Redux

The README.md contains a lot of advanced config examples for functional tasks. We should probably add some basic ones as well:

1. '*.js': ['eslint'] <- fail when eslint finds issues issues
2. '*.js': ['eslint --fix', 'git add'] <- automatically fix eslint issues, and add to commit
3. '*.js': ['prettier --list-different'] <- fail when prettier finds issues
4. `'*.js': ['prettier --write

I've found an unexpected(?) change that stems from #2391.

<Hello name="John" Number="2" />

With {ignoreCase: false}, which according to the docs should take case into account when sorting the props, the above example now expects name to b

i have been using this for a while as i find it a convenient way to tweak eslint settings via eslint conventions, and i just noticed that it wasn't mentioned in the documentation.

should this be documented o

I download the ZIP and run npm install but then I run expo start and I get:

[11:17:11] Starting project at /Volumes/Sata/repositories/snowflake copy
[11:17:12] Expo DevTools is running at http://localhost:19002
[11:17:12] Error: Missing app.json. See https://docs.expo.io/
[11:17:12] No Expo configuration found. Are you sure this is a project directory

How I solve this?

Th

Tell us about your environment

"dependencies": {
    "vue": "2.6.x",
    "vue-meta": "2.3.1",
    "vue-router": "3.1.3",
    "vuedraggable": "^2.23.2",
    "vuetify": "^2.2.2",
 

legacyDecorators parser option should be documented.

The features section in the docs states that nodemon is available in the project, when it's clearly not. It's not added as a dependency or as a command in the project. Maybe remove this from the docs or actually add nodemon?

We loved caniuse-db, but it uses 7 MB and contains many irrelevant data.

This is why @ben-eb created caniuse-lite. It is just a copy of latest caniuse-db (he wrote autorelease script) with less data and better compression. Only 1 MB.

Autoprefixer and Browserslist moved to caniuse-lite. So let’s use it here too. It is very easy, API is the sam

Vscode handles > in tags by calling html/tag and eventually closing the tag.

Example request:

[Trace - 7:58:44 AM] Sending request 'html/tag - (138)'. Params: { "textDocument": { "uri": "file:///home/kyoncho/Sources/lsp-docker/demo-projects/Scala/hello/src/test/scala/example/foo.html" }, "position": { "line": 0, "character": 6 } }

[Trace - 7:58:44 AM] Received response 'html/tag 

Example

I also see the issue with:

• <label>foo<meter /></label>
• <label>foo<output /></label>
• <label>foo<progress /></label>

Workaround
Add the following to your .eslintrc.js

module.exports = { rules:
    'jsx-a11y/label-has-associated-cont

What version of this package are you using?
Not currently using, but about to import this into a project to replace a lot of the existing rules that are part of this
What operating system, Node.js, and npm version?
node: 10.16.0, npm: 6.9.0, os: macOs Mojave 10.14.6
What happened?
From reading https://github.com/standard/eslint-config-standard/blob/master/eslintrc.json and https:

Some folks have noted it would be beneficial to have this repository translated to other languages. One contributor has already volunteered to translate the repository into Russian (woohoo!).

If anyone has the time and drive to help out with other languages, please reply below with the proposed language and I'll give you the "go-ahead"... just to make sure two people don't create translations i

Is this a feature or a bug?

• Feature
• Bug

Please describe the actual behavior.

Today if a new dependency is added to a rush project with rush add (e.g. rush add -p foo) then it will be appended to the end of package.json.

This is not true if a dep is updated to a newer version (e.g. rush add -p foo@~2.0.0 -m) which seems to alphabetize all dependencies cor

use-flow-type doesn't seem to consider "TypeParameterInstantiation" nodes (flow docs examples)

// Reports:
// 'TestType' is defined but never used  no-unused-vars
// Despite being used directly below
type TestType = string

const x = testTypeParam<TestType>("test")

function testTypeParam<T>(in: T)