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 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

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

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?

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

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?

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?

@TimHambourger made a very useful test harness, we could integrate it in our CI somehow (if @TimHambourger is ok with that).

Note we can keep a seperated repo.

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.

A lot of people might understand idea better with hands on example (https://twitter.com/slicknet/status/613412786442350592).

Maybe even replacing whole Let's see an example: of the

x = 0;
if (x) x++;

to analysis of requireCurlyBrackets example

After encountering dependency-check-team/dependency-check#112 I tried looking into how that project uses detective and the various "extensions", such as detective-typescript that enabled foreign syntax. It was not immediately obvious how this worked, seeing no explicit interfaces where detective was wrapped by or passed some "extension"

Could

Prepare the parser to PHP 8 :

• https://wiki.php.net/rfc/union_types_v2

Work In Progress as RFC are not yet closed

At the very least, the rule used for those examples is deprecated, but the whole section could probably use a revamp too.