Was checking babel/babel#11478 and testing out syntax and noticed we don't error with the normal "use this plugin/preset" like we do for proposals with JSX itself. @nicolo-ribaudo mentioned it's probably since jsx is implemented as a normal plugin so we didn't have `this.expectPlugin("recordAndT

Now that Prettier 2.0 has been released with its improved CLI, I think we should add a section do the docs showing a recommended example setup.

1. Recommend using an editor extension that lets you run Prettier from your editor. Link to popular extensions. Maybe add some tips on how to configure for example prettier-vscode.
2. Recommend adding an empty ({}) .prettierrc.json to signify to edit

Issue

When using postcss v7.0.20 the webpack compilation fails with the following stack trace.

✖ ｢wdm｣: TypeError: Cannot read property 'value' of undefined
    at /Users/username/workspaces/terra/terra-core/9.css:220:3
    at new Quoted (/Users/username/workspaces/terra/terra-core/node_modules/postcss-values-parser/lib/nodes/Quoted.js:19:28)
    at cloneNode (/Users/username/works

The ForInStatement and ForOfStatement interfaces can also have VariableDeclaration as the value for the left property, as specified by the spec at https://www.ecma-international.org/ecma-262/10.0/index.html#sec-for-in-and-for-of-statements and demonstrated by running the following code:

esprima.parseScript('for (const a in b) {}');
esprima.parseScript('for (const a of b)

The Error is:

yarn global v1.21.0
[1/4] Resolving packages...
[2/4] Fetching packages...
error An unexpected error occurred: "C:\Users\...\npm-@babel-parser-7.9.4-68a35e6b0319bbc014465be43828300113f2f2e8-integrity\node_modules\@babel\parser\.yarn-metadata.json: Unexpected token \u0000 in JSON at position 0".
info If you think this is a bug, please open a bug report with the informati

Typing print() in the jscodeshift transformer triggers browser print dialog

To Reproduce
Steps to reproduce the behavior:

1. Specify to use jscodeshift
2. Type print() in bottom left corner
3. See the bug

Expected behavior
Shouldn't do that

Browser (please complete the following information):

• OS: OS X
• Browser Chrome
• Version 78.0.3904.108

**astexplorer

Overview of the issue

When I try to include links in the documentation they do not appears as expected.

Operating System, Node.js, npm, compodoc version(s)

node 12.16.1
npm 6.13.4
compodoc 1.1.11 (installed globally)

Angular configuration, a package.json file in the root folder

Compodoc installed globally or locally ?

globally

The spec in https://github.com/estree/estree/blob/master/es2020.md states

bigint property is the string representation of the BigInt value. It doesn't include the suffix n.

Should this represent the source text or a normalized notation?

In other words; is the AST for 1048575n equivalent to that of 0xfffffn or not due to the .bigint field?

Make sure these boxes are checked before submitting your issue - thank you!
(If your issue is neither a both bug nor a request, please write in a free style)

• https://esdoc.org/manual/feature.html
• https://esdoc.org/manual/config.html
• https://esdoc.org/manual/tags.html
• https://esdoc.org/manual/api.html
• https://esdoc.org/manual/faq.html

Short summary of your i

Describe the bug
SQL Server supports assigning a value to a variable from a selected expression.
For example:

DECLARE @var INT;
CREATE TABLE tableName (id INT);

SELECT @var = 1;
SELECT @var = id FROM tableName;

To Reproduce
assertSqlCanBeParsedAndDeparsed("SELECT @var = 1");

System

• SQL Server 2017
• JSqlParser 3.1

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?

Hi I want to check if the prevoius char is a :. The exact example code I have is this:

Prefix: !

I want basicly to be able to check based on if the previous char is a : the ! should get a string and later reuse the look back logic to check if I am inside an array which is defined like in yaml meaning to make sure the last 2 lines of the following example don't get into the ar

Is your feature request related to a problem? Please describe.

No MappedTypeNode definition in ts-morph.
No TypeQueryNode definition in ts-morph.
No TypeOperatorNode definition in ts-morph.

Currently the function page just shows the most recent 200 calls of that function, and doesn't allow going further back.

Basically we need to choose between:

class X {

  private $foo;

  public function __construct(string $foo) {
    $this->foo = $foo;
  }

  public function getFoo(): string {
    return $this->foo;
  }
}

or:

class X {

  /**
   * @var string
   */
  private $foo;

  public function __construct(string $foo) {
    $this->foo = $foo;
  }

  public f

As for Display the special operations generated by the compiler #224 discussion, the documentation will improve if we had a section describing the transformation of each featre and his limitations.

In particular for the special operation, to explain that only the operations that are really generated would appear in the transformation. This is due to the fact that the tool s based on the AST.

from the docs in your readme https://github.com/csstree/csstree/blob/master/docs/parsing.md#atrule

atrule
Type: string or null
Default: null

Using for atrulePrelude context to apply atrule specific parse rules.

What would the string be and how would it be used to apply specific parse rules?

inline templates:

• with anonymous classes
• with lambda

Given input:

if(cond1 || (cond2 && experiments.isToggleEnabled(STALE_FLAG)) {
  // do something
}

the output of PiranhaJava is

if(cond1 || (cond2)) {
  // do something
}

The additional paranthesis around cond2 should be eliminated.