Jordan Pittman

Uring `prettier/plugins/flow` directly reproduces the issue: ``` import "prettier/plugins/flow"; throw new Error("test"); ``` That plugin doesn't do anything weird but it does import (and subsequently bundle) `flow-parser` which also reproduces...

I think this is because of the OCaml byte code -> JS compiler that flow uses (`ocaml_of_js`). I'll open an issue on the Flow repo about this. I'm not sure...

Opened a bug report: https://github.com/facebook/flow/issues/9299 To my knowledge there is no way for us to lazy load this currently. I saw Prettier is working on making `preprocess` async-capable in newer...

Doesn't this imply that you *have* to use a version of node where `require(esm)` is enabled? afaik the only reason this would fail is because `require(…)` is being used instead...

Closing in favor of #15289

I think this was fixed in Lightning CSS 1.30.0 and we did a release back in May that updated to v1.30.1. I also verified that the reproduction no longer errors....

We had someone actually request this one but it was long enough ago that maybe we can drop support for it. It doesn't really cause problems keeping support for it...

Lightning CSS doesn't appear to remove the duplicate `content` property. There being an extra one isn't really a big deal but maybe this is a micro optimization we can make...

I've implemented an optimization that should clean this up. Will be in the next release. 👍

what templating language is this? Angular?