https://eslint.org/docs/rules/use-isnan

This is a proposal to modify the use-isnan rule.

Current rule setting:

use-isnan: "error"

Proposed rule setting:

["error", {"enforceForSwitchCase": true}]

The switch statement internally uses the === comparison to match the expression's value to a case clause.
Therefore, it can never match _case NaN. Also, `swit

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

The callable constructor proposal was withdrawn because "the same problems can be solved with decorators" but the readme here doesn't show examples of that. Can you please update that for reference? It would be really helpful.

We also use other inappropriate notation such as "Promise object". We should fix the inconsistencies.

Are there any plans to submit SWC to the Kangax compatibility table. This is my (and I think most web developer's) goto resource when trying to determine which ES features a given project supports. It includes all common web browsers, as well as babel and typescript. I believe it also comes with a test suite.

https://kangax.github.io/compat-table/es6/ (+ the next version).

I would love to us

I want to use eslint's autofix to fix layouts only.
Like this: eslint --fix --fix-type layout
(--fix-type: https://eslint.org/docs/user-guide/command-line-interface#fix-type )
To work that one plugin's rules must contains the type field.
( the type field: https://eslint.org/docs/developer-guide/working-with-rules#rule-basics )
Are there any reasons why this field cannot be added?

Multiple different Javascript snippets can result in a LineComment node:

// type1
<!-- type2
--> type3

From current Esprima's output there's no way to know which one of these 'styles' was used as a comment.

Since this is specific to LineComment nodes, it's possible to split the type of node from 'LineComment' into 3 node types (one for each style). But I assume that wo

嗨, 您好
在學習CH05的時候,遇到一個問題
發現在 webpack.config.js 裡面的 module: { preLoaders: [ { ... } ],
似乎造成webpack錯誤 無法執行

如下terminal截圖

稍微查了一下,解決方法是用 webpack@2.1.0-beta.22 版本
我目前是 "webpack": "^2.2.0", _應該也

get rewritten into

[
    1,
    2
]

which is not what one would expect rewriting the code. That's a small, innocent literal array. And yet I see no way to make escodegen output such lists as [1, 2]. Could you add it as a default behaviour and an option, please?

What version of this package are you using?
"eslint-config-standard": "^14.1.0"

What operating system, Node.js, and npm version?
node.js is 10.18.0 and npm version is 6.13.4

What happened?
when i use this npm with eslint, it get something wrong to notice me the errors in the javascript file of my project.like this error:
1:1 error Definition for rule 'no-async-promise-ex

Nice work!
But as an embeddable engine, I think it would also be nice to provide some API functions for the other languages to use.

On Win10 (tested in FF), the top right logo font is bolder than on MacOS, causing the text to overflow the 210px given space.

Adjust the font to look more the same, e.g. reducing the font-weight from 800 to 600-ish on Windows should fix it.

README states:

Why not use WebAssembly?

There are massive existing untyped codebases, and there is no easy way to convert an untyped, garbage collected language to WebAssembly. And even if there were, there is no guarantee that it would be any faster to transmit/parse/start than what we currently have.

whereas WebAssembly FAQ states:

The kind of binary format being considered f

Second Example in the README.md: Shouldn't it be "return this.break();" instead of only "this.break();" in order for the traversal to end at the first node?

In the Stylistic Issues section, it's mentioned that both URLSearchParams and URL are defined as global variables.

I think this was introduced by this commit nodejs/node@3124146 which match release 10.0.0.

My current runtime is 8.10 (the latest version supported by AWS lambda atm). It seems that this variables were added to the global scope after that

The generated code works without errors for js, however the generated ts definitions might contain bugs although this isn't critical at runtime it can cause confusion at dev time.

A report should be generated for all modules inside the generator directory after a build is done.

The task should be more or less as follows:

1. Run the generator
2. Run npm cache to cache the undeployed packa

In a few places in the code, assert is require'd and used to throw a simple error.

You should remove this and simply 'throw new Error(...)'. The benefit of doing so is that it shrinks the browserify'd library considerably.

Requested Update

I was asked today if there was a tool to check if the transpiled code was ES5 and I referred to this project but I just checked and es-check es5 ... does not catch Promise from ES2015.

Why Is This Update Needed?

The reason I was asked is that they have continuous issues with bug reports because they forget to add polyfills to their projects. They need an automated w

As of #304, we progressively import shared references into the content stream, handing them out dense numbers.

We should probably do the same with prelude references, producing a content stream that dynamically assigns consecutive numbers to shared references and prelude references. This may be further improve compression and/or let us better find patterns that work across shared and prelude re