Kevin Gibbons

@duailibe I think a "disable all template literal formatting" flag would be more useful, at least pending a more general design (e.g., factoring all literal formatting out into plugins which...

https://github.com/prettier/prettier/pull/7875 does not disable it by default, but does add an option which allows you to disable formatting all embedded code across the board. We can continue to discuss more...

> I think not breaking imports onto multiple lines could help with this. That'd make me sad. Minified code will tend to have all of its imports on the same...

Oh! Forgive me, I misunderstood. That seems fine to me. (Doing it unconditionally, anyway; I don't think it would be worth adding an option.)

I don't think it would make sense to build this into Prettier, but we've been talking (https://github.com/prettier/prettier/issues/4424) for a long time about adding a plugin API for embedded language formatting,...

There's not usually a single fragment of the ES spec to which a given proposal corresponds - most proposals touch parts across many sections.

> (separately, the single-page, not the multi page, version of the spec is the canonical one and ideally everyone external only links to the single-page version) It's true that the...

@kitsune7 I intend to add support for hex, but am unconvinced by the need for base32; see https://github.com/tc39/proposal-arraybuffer-base64/issues/7#issuecomment-872536851. But let's continue the conversation on that repository rather than here.

Sweet, LGTM! > @bakkot the readme needs to be updated! Yeah, I'm still catching up on stuff from the meeting, sorry.

@isiahmeadows: > every single one of them had to be trivially desugared As you correctly point out, engines already do these sorts of simple translations, often at parse time. What's...