SUZUKI Sosuke

Upgrading postcss-values-parser may help to avoid this problem

note: We need to support Vue SFC custom blocks (context: https://github.com/prettier/prettier/pull/8023#discussion_r407216429)

I cannot reproduce this in playground. Can you reproduce in playground? **Prettier 2.3.2** [Playground link](https://prettier.io/playground/#N4Igxg9gdgLgprEAuEAeAhAEQPIGEAqAmgAoCiABABYwC2ANgHwA6Uq195dAhlAOYC8TEAiHNWlOFwAmY8uVQ04MLuTCUuAJwDOSwSACq+AGIBaAByiWchUpXUYABxNwAjgFcAlgDc9ADRP6AIImuBA0DlwwHgBGdHBCqtDwsHoAkqT8cFK88SCy8orK5FBcinpeHnAA7g4QGjAJkLAIMHpVHlIwlPxScBVgcCbtnZQANOQeUB5RXHQmWmCzcPwAjAB0AAyWUNZRMHEMmBBgboqwqAD0ewcslxLSYqjREFIAnvm3F89vjxfsjCBRiAIA4otAtMhQJoNBAqsRNAgIShZlUuK8IUDohouGAANZKADKETAk14yBgGjccCBcBo0SyvSkABkeLw3FwckY6jRIlE+MgQFw3DAIICQP8AOqUaZwLTEuAExHTbzTV4CsBaDEgSY6erEbG8HnIABmsx0QIAVloAB4AIWxeMJpTgTMmcBNZupICt1oJpLiAEU3BB4B66OaQBFtHANAL-mKHBpJjAJR0usgzBsgYmIDoJdiHALE7KY153UD3CG4PqQUjBVoTFA4FksmKNK5PO39RyjUhTeGvToaB5yZTB-64EGq2GI8poqmRsgAExAilcDx0UmhGi94RaACsYrcOnwXGiSP7Ea8VNSUF6sAJYCToMCd4JMFecRncAAvj+gA) ```sh --parser html ``` **Input:** ```html Document ``` **Output:** ```html Document ```

Range ignoring is already proposed(#5287)!

pros and cons I think other than what fisker gives: **Pros** - Easy to understand to usage of AST especially for first-time contributors. **Cons** - It's a refactoring with a...

> Formatting changes aren't considered breaking, are they? Also the new logic doesn't remove those spaces. It preserves them as they are. Reformatting with the new version shouldn't lead to...

@tats-u > can I export these constants or make them global? Yes. We can export these variables from `language-markdown/utils.js`. Please move to module top-level and add identifiers into `export {...

I think we can remove it if it isn't used by real-world plugins.

I agree with @kachkaev . We need to more discuss making `useTabs` default. At least, I don't think we should do it in 2.0 because the discussion is not still...

Remark and MDX ecosystems use Pure ECMAScript Modules Packages. We need to use that parser, and I think the our ECMAScript Modules migration(#10157) block this work.