| Age | Commit message (Collapse) | Author |
|---|
|
Since the async parts of the spec are not stage 3 at this point we don't
add AsyncDisposableStack.
|
|
The using declarations have kind of special behavior in for loops so
this is seperated.
|
|
In this patch only top level and not the more complicated for loop using
statements are supported. Also, as noted in the latest meeting of tc39
async parts of the spec are not stage 3 thus not included.
|
|
This is an export which looks like `export {} from "module"`, and
although it doesn't have any real export entries it should still add
"module" to the required modules to load.
|
|
These are now formatted just fine and no longer cause errors or
unintended formatting changes.
|
|
We didn't initially upgrade because it started to (incorrectly) see
files as strict mode and chokes on things that then would be syntax
errors - but we're starting to fall behind a bit, so I'd rather put
these files on the ignore list instead.
|
|
For example, "property.br\u{64}wn" should resolve to "property.brown".
To support this behavior, this commit changes the Token class to hold
both the evaluated identifier name and a view into the original source
for the unevaluated name. There are some contexts in which identifiers
are not allowed to contain Unicode escape sequences; for example, export
statements of the form "export {} from foo.js" forbid escapes in the
identifier "from".
The test file is added to .prettierignore because prettier will replace
all escaped Unicode sequences with their unescaped value.
|
|
eval only has direct access to the local scope when accessed through
the name eval. This includes locals named eval, because of course it
does.
|
|
This is a script similar to the clang-format one to ensure prettier
formatting of most JavaScript files.
|
|
Also use "// prettier-ignore" comments where necessary rather than
excluding whole files (via .prettierignore).
|
|
|
