Richard Gibson

Agreed. My intention is to split the problem in two... on one side, generating diff information in a format like [JSON Patch](https://tools.ietf.org/html/rfc6902), and on the other, rendering the diff.

This produces lots of failures like the following; how do I update the [TAP] test expectations in bulk? ``` not ok 43 - should be equal --- compare: === at:...

Found it: https://github.com/avajs/ava/blob/main/test-tap/reporters/readme.md

> I agree with almost everything. However, I'm not a big fan of the `PASS:` and `FAIL:` noise. I think the icons are clear enough for the common case and...

https://github.com/jquery/sizzle/issues/342#issuecomment-487648220 > that call to `uniqueSort` is specific to use of multiple positional matchers like `:first`, `:last`, `:even`, `:odd`, `:eq(N)`, `:lt(N)`, and `:gt(N)`, all of which are ill-advised and deprecated....

`cooked` and `value` (elsewhere `raw`) properties in the `value` of a TemplateElement should correspond respectively to `cookedValue` (TV; Template Value) and `rawValue` (TRV; Template Raw Value) in the [template runtime...

I have that same hope, but doing it right means representing program source in a way that is agnostic of AST node type—no special treatment for nodes that happen to...

> `type: "BlockStatement"` Don't you mean `type: "DoExpression"`?

Yes, subject to the concerns about completions @michaelficarra mentioned. But `{ "type: "BlockStatement", "body": […] }` is an existing AST node, and [it isn't an Expression](https://github.com/estree/estree/blob/master/es5.md#blockstatement).

I thought about that, but `type` would collide with the Node property. Honestly, though, there's no relevant ECMAScript-level distinction. The key detail in _this_ representation is `reference` vs. `value`, which...