Skip to content

Commit

Permalink
[blog] fix proposal stages
Browse files Browse the repository at this point in the history
  • Loading branch information
ahuglajbclajep committed Aug 24, 2020
1 parent 2fe0415 commit 7e5f6b9
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions website/blog/2020-08-24-2.1.0.md
Expand Up @@ -416,7 +416,7 @@ for (const element of list) {

#### Support Private Fields in `in` ([#8431](https://github.com/prettier/prettier/pull/8431) by [@sosukesuzuki](https://github.com/sosukesuzuki))

Support Stage-2 proposal [Private Fields in `in`](https://github.com/tc39/proposal-private-fields-in-in/blob/master/README.md).
Support Stage-2 proposal [Private Fields in `in`](https://github.com/tc39/proposal-private-fields-in-in).

<!-- prettier-ignore -->
```js
Expand All @@ -435,7 +435,7 @@ SyntaxError: Unexpected token (1:1)

#### Support ES Module Attributes and JSON modules ([#8436](https://github.com/prettier/prettier/pull/8436) by [@fisker](https://github.com/fisker))

Support Stage-1 proposal [ES Module Attributes and JSON modules](https://github.com/tc39/proposal-module-attributes).
Support Stage-2 proposal [ES Module Attributes and JSON modules](https://github.com/tc39/proposal-import-assertions).

<!-- prettier-ignore -->
```js
Expand All @@ -453,7 +453,7 @@ import foo from "foo.json" with type: "json";

#### Support record and tuple syntax ([#8453](https://github.com/prettier/prettier/pull/8453) by [@fisker](https://github.com/fisker))

Support Stage-1 proposal [JavaScript Records & Tuples Proposal](https://github.com/tc39/proposal-record-tuple/blob/master/README.md).
Support Stage-2 proposal [JavaScript Records & Tuples Proposal](https://github.com/tc39/proposal-record-tuple).

_Only support `#[]`/`#{}` syntax, not `{| |}` / `[| |]`._

Expand Down Expand Up @@ -1255,7 +1255,7 @@ Non-ASCII whitespace characters like `U+00A0` `U+2005` etc. are not considered w
Previously we parse html `<script>` blocks as "module"([ECMAScript Module grammar](https://babeljs.io/docs/en/options#sourcetype)), this is why we can't parse comments starts with `<!--`(aka [HTML-like comments](https://tc39.es/ecma262/#sec-html-like-comments)), now we parse `<script>` blocks as "script", unless this `<script>`
1. `type="module"`
2. `type="text/babel"` and `data-type="module"`, [will be introduced in babel@v7.10.0](https://github.com/babel/babel/pull/11466)
2. `type="text/babel"` and `data-type="module"`, [introduced in babel@v7.10.0](https://github.com/babel/babel/pull/11466)
<!-- prettier-ignore -->
```html
Expand Down

0 comments on commit 7e5f6b9

Please sign in to comment.